Monday, November 23, 2009

Check B4 saying Yes

1. How to tune RMAN performance?
2. What are the major difference between 9i RAC and 10g RAC?
3. What is the PGA_AGGREEGATE_SIZE?
4. What do you understand from MVIEW?
5. What is TAF?
6. What is the use of OCR and voting disk?
7. What happens when a user commits?
8. How to create duplicate database?
9. Steps to install RAC?
10. Steps to recover control files through RMAN?
11. Steps to configure DataGuard?
12. How to sync Primary to secondary if archived log files are deleted?
13. What are new features introduces in Oracle database 10g?
14. What is new feature in RMAN in 10g and 11g?
15. How will you check the status of 10 databases instances running on two node clusters?
16. How will you delete the first letter of first 100 hundred lines in VI editor?

Tuesday, June 16, 2009

Password while creating the Database

Hi Reader,
never specify the "@" in the password field while creating the database with DBCA.
I suffrred the same problem for 4 days after that I got to know this thing.

Monday, June 15, 2009

VIPCA on Cent OS 5.3

6.9 SRVCTL and VIPCA Utilities Set the LD_ASSUME_KERNEL Parameter

The SRVCTL and VIPCA utilities shipped with Oracle Database 10g release 2 and Oracle Clusterware software set the environmental variable LD_ASSUME_KERNEL. On SUSE Linux Enterprise Server 10, because the older Linux threads API has been removed from GLIBC, setting this parameter causes the SRVCTL and VIPCA utilities to exit with the following error:

/opt/oracle/crs/jdk/jre/bin/java:

error while loading shared libraries:

libpthread.so.0: cannot open shared object file:

No such file or directory

Workaround: Comment out the lines that set the LD_ASSUME_KERNEL variable from the VIPCA and SRVCTL utilities. For the VIPCA utility alter the $CRS_HOME/bin/vipca script commenting out lines 119 through 123 as follows:

arch='uname -m'

# if [ "$arch" = "i686" -o "$arch" = "ia64" -o "$arch" = "x86_64" ]

# then

# LD_ASSUME_KERNEL=2.4.19

# export LD_ASSUME_KERNEL

# fi

With the lines commented out, root.sh should be able to call VIPCA successfully. Ensure that you do not to comment out line 118 which sets the arch variable as that is needed by the script.

For the SRVCTL utility alter the $CRS_HOME/bin/srvctl and the $ORACLE_HOME/bin/srvctl scripts commenting out lines 173 and 174 as follows: