| testing RAC [message #455996] |
Fri, 14 May 2010 00:35  |
malhi
Messages: 96
Registered: December 2009
Location: Karachi
|
Member |
|
|
We are testing RAC implemented by a vendor on oracle 11gr1. I observe following, kindly tell me whether it should be like this
1. I update a column of a table on one node and terminate the session without commiting. I checked it was applied. (My understanding is that when we close s session without commit, it rollback )
2. Same happens in insert case.
3. I issue a time consuming update/Insert , and before it ends it close session. (Nothing was applied)
Can you please help, what should i do for further testing.
We are using
Oracle Enterprise Linux 5.4
DRBD 0.8.3 (Dual Primary Mode)
OCFS2 1.4.4
Oracle Clusterware 11.1
Oracle RDBMS 11gr1
|
|
|
|
|
|
|
|
|
|
| Re: testing RAC [message #456050 is a reply to message #456025] |
Fri, 14 May 2010 05:13  |
malhi
Messages: 96
Registered: December 2009
Location: Karachi
|
Member |
|
|
what is your opinion about three points, regarding which i enquire.
If you can tell me what should be the criteria of testing.
|
|
|
|
|
|
|
|
|
|
| Re: testing RAC [message #456946 is a reply to message #456875] |
Thu, 20 May 2010 07:20 |
malhi
Messages: 96
Registered: December 2009
Location: Karachi
|
Member |
|
|
When i login as "sqlplus / as sysdba"
then whatever i update or insert and kill session, without commit it behave exactly what i mentioned at 1 & 2.
But when i login as "sqlplus taq/pwd@node" and do some update or insert and kill session, without commit it rollback.
In both cases autocommit was off. I could not understand this difference.
|
|
|
|
| Re: testing RAC [message #456957 is a reply to message #456946] |
Thu, 20 May 2010 07:51 |
 |
Michel Cadot
Messages: 68716
Registered: March 2007
Location: Saint-Maur, France, https...
|
Senior Member
Account Moderator |
|
|
- Never ever use SYS (or SYSDBA) but for maintenance purpose (startup, shutdown, backup, recover)
- SYS/SYSDBA is special
- SYS/SYSDBA is Oracle proprietary (try to open a SR/TAR starting with "i did that with SYS/SYSDBA" and you'll see the immediate answer)
- SYS/SYSDBA does not act like any other user
- When you use SYS/SYSDBA Oracle deactivates some code path and activates others
- Whatever you do with SYS/SYSDBA will neither validate nor invalidate the same thing with any other user.
NEVER EVER use SYS/SYSDBA for anything that can be done by another user.
Use SYS/SYSDBA ONLY for something that can't be done by someone else.
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
