Checklist for debugging OracleCM Service9i startup problems:
————————————————————-
1.Check the priority of the OracleCMService9i from task manager.It should be set to high.Refer to metalink note 255481.1 for the same.
2.Check whether all the network interfaces are enabled on both the nodes and the bninding order too.Fire the command ipconfig /all on both the nodes and check whether both the public and private interfaces are listed in the order public-first and then private.None of the interfaces should be disabled.
3.Check whether the shared disk is visible on both the nodes or not(check by going into the computer management -> disk management).If the shared disk is not visible or asking for ” whether you want to format the disk?” fire the following command on the node from whether the shared disk is not acessible:
ocfsutil /c OnlineVol /m
4.Check whether the DHCP service is enabled or not.If enabled, disable it.Refer to the following URL for further details:
http://support.microsoft.com/default.aspx?scid=kb;en-us;239924
5. Check in the event log of the nodes whether there is any error pertaining to the Windows time service.The time on both the nodes should be perfectly synchronised.If there are any errors pertaining to the Windows Time service, the following comand should be fired on both the nodes to make them in sync: w32tm /s.
6.Check for the following dependencies in the registry.
The OracleCMService9i should have a dependency set on OraFenceService (Mother of all services in a RAC setup;not visible in registry but can be checked out in MyComputer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\).
The instances should have a dependency set on the OracleCMService9i for autostartup of the databases in a RAC environment.
The service inter-dependency tree in a 9i RAC environment is as follows:
Oracle Database Service
|
v
OracleCMService9i
|
v
OraFenceService
The DependOnService keyword value for the services should be refelecting the above dependency tree on both the nodes.
Refer to metalink note ID:300762.1 for further details.
Hi all,
today I am going to discuss about a oracle error which every DBA must have faced in his/her career i.e ora-257
Ora-257 is mainly caused when archiver is unable to archive the online redo log files at the desired location.If this error is ignored it may cause instance crash to safeguard the recovery of database.
In order to solve the above error the solutions are
1.) Increase the free space where archiver archives the archivelog. The location where archiver archives the log is determined by parameter file pfile or spfile.
This can be determined by loging into sqlplus and issuing
SQL> show parameter log_archive_dest
2.) In case it is not possible to increase free space at the same location but if free space is available at other location then the parameter log_archive_dest (or log_archive_dest_1 in some cases) can be changed so that the new archives are produced at new location specified which has free space.
this can be done by modify init.ora file or using alter system if spfile is present
SQL> alter system set log_archive_dest_1=’
3.) The option which is often used is to take a backup of the archives from the existing place and delete those archives from that place so that new archives can generated at that place .
the backup can be OS level backup and OS level del;etion but the recommended method which is compulsory to be used with ASM in place is taking any RMAN backup and delete using RMAN. as shown
rman target sys/sys
RMAN> backup archive log all device type disk format ‘/oracle/arch_%U’;
RMAN> delete archive until time ‘trunc(sysdate)’;
This will delete all the archive logs until today and space will freed and the archiver will start archiving redo logs
