Tag Info

Hot answers tagged

2

The easiest way to register your listener at Oracle Grid Infrastructure is to run netca. If you want to configure the listener "LISTENER" you have to make sure that it does not exist in the listener.ora yet. One more thing: You should always configure your own host in the /etc/hosts file.


2

The only correct way to back up an Oracle database is to use RMAN. There are alternatives but they are not as reliable as RMAN. RMAN has a ton of features and this might make it look complicated. But in fact it's not difficult and should always be the choice to back up a database. RMAN does not do logical backups like tables, indexes, procedures. RMAN does ...


2

There are some things which have to be set up correctly: The user you are logged on has to be a member of the ora_dba operating system group. The parameter SQLNET.AUTHENTICATION_SERVICES=(NTS) must be set correctly. It can include more options but "NTS" is required. You have to connect to the database correctly which is: sqlplus / as sysdba. You can also ...


2

Which Database Version do you have? From Oracle 11g onward you should be using the SCAN listener. The SCAN listener knows where the database is located in the RAC and how much load is on that node. Further more you should define services for long ops and short ops for better load balancing.


1

du of asmcmd doesn't support this, just put it in a loop. $ dg=fra; for dir in $(asmcmd ls $dg); do echo $dg/$dir; asmcmd du $dg/$dir; done


1

Just from Oracle side there is nothing to worry about. You could even do this operation during normal business hours. BUT! most Applications are not cluster ready. They cannot deal with this situation and will crash. All services are still available since they are migrated to the second node. But the session does not get migrated that's why the client will ...


1

The problem is the locking in the SGA that effectively cause the the concurrency is going down. This kind of apps make the database a close to single user platform instead of a highly scalable and concurrent accessible database. The cause of this is that the connections have to be maintained in a shared memory table where inserting and deleting means locking ...


1

This (old) Oracle document 67137.1 Load Balancing and DESCRIPTION_LISTs1 says the following about the effects of multiple DESCRIPTION elements: When SQL*Net reads a TNS alias with a DESCRIPTION_LIST, it flips a coin to select which description to use to connect. This randomization is what provides us with our Load Balancing feature. It further ...


1

Just make sure auto controlfile backup is turned on. If you added or dropped a datafile(s) before the controlfile was backed up, and you had a hardware failure which resulted in the single CF not be accessible, it would be a pain to restore...not impossible, just a huge pain and a time sink during a sensitive time resuming services. Cheers, JD


1

Oracle has spoken: http://docs.oracle.com/cd/B19306_01/server.102/b14231/ds_txnman.htm#i1008473 Distributed Query Returns Different Results on Consecutive Runs when no Changes Exist in the Base Tables. (Doc ID 561471.1) ...skip some more writing... Bug.611416 SELECT AFTER UPDATE AND COMMIT DOESN'T SHOW UPDATED COLUMNS ...skip some more ...


1

crsctl status resource -t clearly shows the cause of the problem, the listener is not registered in the clusterware. Undo all changes in listener.ora (or simply delete it), then: srvctl add listener srvctl start listener



Only top voted, non community-wiki answers of a minimum length are eligible