log4j:WARN No appenders could be found for logger (oracle.sysman.emSDK.svlt.EMServletUtil).
log4j:WARN Please initialize the log4j system properly.
ConnectionService.init: Get repos properties from credential store.
Repos details fetched from credstore
Fetched repository credentials from Credential Store
OMS version 11.1.0.1.0 is not compatible with repository version 10.2.0.4.0 Repository needs to be upgraded.

However, i know that our DB is 11.1.0.7.0 , so not sure why OMS thinks the version is old? any pointers?

How can we change this port and which service we need to restart.

Enjoyed reading your article on exporting and importing database stats.

Could you give me some help, or maybe write a new page, on how to do individual tables and schemas too.

Thanks.

This just solved an hour's head scratching here in the office.

Many thanks :-)

 ALTER TABLE <table name> RENAME CONSTRAINT <constraint name> TO <new constraint name> 

Mike

thank you

Grid Control
Oracle Enterprise Manager. Used to monitor, manage and tune databases, servers, listeners and other targets.

Grid Infrastructure
A new product "grouping" introduced with Oracle 11g. Currently, it contains ASM, HAS and Clusterware.

Grid Infrastructure is need for ASM as this is how you install the ASM binaries.

Grid Control is not needed for ASM to install ASM.

Hope this helps.

I don't know how you came across this answer, but it's genius! I was just about raise an SR with Oracle for this one having wasted the last couple of hours googling and re-installing things all to no avail when someone told me they'd seen this entry on the forum.

Thanks again!

Regards

Thanks

In the end we implemented ODM/quick IO as this significantly improves throughput on Veritas filesystems. Alternatively, if possible try an alternative filesystem. UFS instead of VxFS. Be aware, that quick IO was a cost option.

http://abcdba.com/abcdbarachowtoinstallrac10gonsolaris1of4

HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\inst_loc

The value should be set to the location of your inventory.

If it is not set, locate the inventory on your C drive and modify the inst_loc value to the full path of your inventory.

If it is set then check that the value is correct.

If you do not have an inventory, then delete the inst_loc key

dup_rows=`cat input.csv |sort |uniq |wc -l`
if [ $dup_rows -eq $num_rows ]
then echo "No Duplicates"
else echo "Duplicates" |mailx -s "Duplicate Rows in File" email_address
fi

Does this help?

cat logfile |mailx -s "Report to Users" email_address

However, if you want to check the file using the unix shell script then the best way to achieve this is as follows

1) The script should count the number of line in the Input.csv file and send an email to the users.

num_rows=`cat input.csv |wc -l`
echo $num_rows » someoutputfile.txt
cat someoutputfile.txt |mailx -s "Report to Users" email_address

2) The script should notify the users the the Input.csv file contains duplicate records in it (if any duplicate records exists).

dup_rows=`cat input.csv |sort |uniq |wc -l`
if [ $dup_rows -eq $num_rows ]
then "No Duplicates"
else cat "Duplicates" |mailx -s "Duplicate Rows in File" email_address
fi

3) If no duplicate records exists in the input.csv file and the data gets loaded into the Oracle table, the script should calculate the total no.

The above code has already established this. i.e. row_nums

Mike

#Checks whether the Inpu
t file exists. If file found the load process starts else throws error that file not found

if [ -f $file ]
then

if [ $(hostname) = elect ]
then
export userName="zx01182"
export ORACLE_SID=db86
export pwd_file=db86zx01182pw
elif [ $(hostname) = chi ]
then
export userName="zx01204"
export ORACLE_SID=db87
export pwd_file=db87zx01204pw
elif [ $(hostname) = zack ]
then
export userName="zx01205"
export ORACLE_SID=db88
export pwd_file=db88zx01205pw
else exit
fi

/usr/local/pl/util_scripts/perlencrypt.pl -k /export/home/oracle/secure/ealgorithm -d /sdr1/system/$pwd_file | sqlplus $userName @/space/dbexport/scripts/tr
uncate_phr_bene_1.sql

/usr/local/pl/util_scripts/perlencrypt.pl -k /export/home/oracle/secure/ealgorithm -d /sdr1/system/$pwd_file | sqlldr $userName control=$ControlFileNm log=
$logfile bad=/space/dbexport/PHR/bad/bene_eligibility-`date +%Y%m%d`.bad

rc=$?
if [ $rc == 0 ]
then
echo 'Bene_eligiblity table load Successful'
mv /space/dbexport/PHR/data/eligExport.csv /space/dbexport/PHR/archive/eligExport-‘date +%Y%m%d`.csv
chmod 640 /space/dbexport/PHR/archive/eligExport-`date +%Y%m%d`.csv
exit $rcelif [ $rc == 0 ]
then
echo ’Bene_eligiblity table load Successful'
mv /space/dbexport/PHR/data/eligExport.csv /space/dbexport/PHR/archive/eligExport-‘date +%Y%m%d`.csv
chmod 640 /space/dbexport/PHR/archive/eligExport-`date +%Y%m%d`.csv
/space/dbexport/PHR/log/bene_eligibility-`date +%Y%m%d`.log | to=moc.naidiron|55311di#moc.naidiron|55311di
basename=`basename $logfile`
subject="BENE ELIGIBILITY TABLE LOAD STATUS"
( echo ’BENE ELIGIBILTY LOAD PROCESS FINISHED SUCCESSFULLY'; uuencode $logfile $basename ) | mailx -s "$subje#ct" "$to"
status=`cat $variable`
status=`cat $logfile`
exit $rc

I need this script in Unix. Can anyone please help me out with this..

Regards

why

RMAN-08138: WARNING: archived log not deleted - must create more backups

Mike

The current open cursor alert in Grid Control is per database.

Therefore, if open_cursors is set to 500 on your database then it is perfectly concievable that you will break the current open cursor alert in grid. You should increase the threshold for the current open cursor alert to a more realistic value.

Regards

how can this be?

See the following links

http://oracle-wiki.net/startdocsgridcontrolsolarisagentinstall - 10g

http://oracle-wiki.net/startdocsgridcontrollinuxagentinstall11g - 11g

Check the project ID of Oracle and Root.

 su - oracle oracle> id -p uid=6869(oracle) gid=900(dba) projid=100(user.oracle) 

Repeat for root.

If you have a projid which is different (e.g. projid=1(user.root)) then possibly pam.conf is bad.

Check the su section of the /etc/pam.conf file

 su auth requisite sst_pam_sys_sec.so.1 su auth requisite pam_authtok_get.so.1 su auth required pam_unix_auth.so.1 su auth required pam_unix_cred.so.1 

If the last entry above isn't there, then add it. If this line is missing it can lead to RBAC permission errors as well.

to see what it is set to.

 sysctl net.ipv4.ip_local_port_range 

Then you should be able to change the range by running (as root)

 sysctl -w net.ipv4.ip_local_port_range="1024 64000" 

Finally, to make the change permanent update your sysctl.conf file with

 # increase system IP port limits net.ipv4.ip_local_port_range = 1024 65535 

What DB?
What Version of VCS?
What OS?

I had this problem and it turned out that I had a faulty network card on my heart beat LAN which had been configured to use IPMP. The obvious solution is to get the network card fixed, but if like me, you needed to get the database working asap, then the simpliest thing is to tell the Clusterware to ignore the failing card. To do this, log on as root as isse the following commad:

$CRS_HOME/bin/oifcfg delif -global <network card name>

Assuming the heartbeat LAN will still function using the surviving network card pairing you should find dbca will now work.

Good luck,

Kore.

 ORA-27504: IPC error creating OSD context ORA-27300: OS system dependent operation:check if cable failed with status: 0 ORA-27301: OS failure message: Error 0 ORA-27302: failure occurred at: skgxpcini1 ORA-27303: additional information: requested interface nxge1 interface not runni ng set _disable_interface_checking = TRUE to disable this check for single insta nce cluster. Check output from ifco 

Can anyone help? Thanks in advance.

http://download.oracle.com/docs/cd/B19306_01/server.102/b14231/create.htm#sthref444

ORA-27102: out of memory
SVR4 Error: 22: Invalid argument

GUIDELINES

1. Every script should be tested.

2. Scripts submitted should contain a script header.

3. Preferably, documentation should be contained within the script header. Alternatively, if the documentation is particularly detailed or large, it should be uploaded to the site with the script or a link provided to an external source.

4. Where applicable, details of the database version, O/S version and O/S name that the script runs against should be present in the script header.

5. A brief description of what the script does should also be in the script header.

Where possible, admins will test the script before it is submitted to the scripts section. (Subject to platform and major version availability and admin resources)

AND FINALLY

It should go without saying,

• NEVER run any script in production systems before testing on YOUR own test environment.

• ALWAYS read the documentation provided with the scripts

• AT LEAST try to understand what it is your running before running it. DONT RUN THE SCRIPTS BLIND.

DISCLAIMER

The nature of scripting is that bugs will be present in all but the most basic scripts. Therefore, no guarantee, warrantee or endorsement is given to any of the scripts on this site. The use of these scripts is done so entirely at the discretion and risk of the person running them.