Hi,
As I have suggested to check the progress of the dataguard use the following query
SQL> select status,error from v$archived_dest where dest_id = (dest-id of log_archive_dest_integer );
STATUS ERROR
———————————————————————————
VALID
And to put the physical standby in recovery mode use the following query.
SQL> alter database recover managed standby database disconnect from session;
However when u use the following query
SQL> recover managed standby database disconnect from session;
to put the standby in recovery mode u can sometimes get following error
From primary
SQL> SQL> select status,error from v$archived_dest where dest_id = (dest-id of log_archive_dest_integer );
STATUS ERROR
———————————————————————————————
Ora-1010 invalid oci operation
OR
STATUS ERROR
———————————————————————————————
ora-12152 TNS send break message
Hence to avoid such error always use the following query to put the physical standby in recovery mode
SQL> alter database recover managed standby database disconnect from session;
Hi,
In 10gR2 RAC on IBM AIX we had a database when starting the database in nomount stage we got the following error
SQL> startup nomount
ORA-27504: IPC error creating OSD context
ORA-27300: OS system dependent operation:sendmsg failed with status: 59
ORA-27301: OS failure message: Message too long
ORA-27302: failure occurred at: sskgxpsnd1
However when the root cause of error was improper tcp udp parameter settings which is required in an RAC environment for cache fusion.
The following is the required settings for tcp-udp parameter for RAC environment on IBM-AIX systems
Using the following commands change the values of the following parameters(in AIX):
# no -o tcp_sendspace=262144
# no -o tcp_recvspace=262144
# no -o udp_sendspace=65536
# no -o udp_recvspace=262144
Also the parameter rfc1323 needs to be set to 1 for any TCP/ UDP parameters settings of
over 64K.
no -o rfc1323=1
Adding these entries to /etc/rc.net will ensure that the parameter take effect on every reboot.
Also, the following are the appropriate ulimit settings for RAC environment on IBM AIX systems
As a root user, add the following entries for the root and Oracle users:
root:
fsize = -1
core = 2097151
cpu = -1
data = -1
rss = -1
stack = -1
nofiles = -1
oracle:
fsize = -1
core = 2097151
cpu = -1
data = -1
rss = -1
stack = -1
nofiles = -1
This needs to be done on all nodes of the cluster. A server reboot might be necessary to activate updated limits. After you modify the settings, the “ulimit –a†command should display the following:
# ulimit –a
time(seconds) unlimited
file(blocks) unlimited
data(kbytes) unlimited
stack(kbytes) 2097152
memory(kbytes) unlimited
coredump(blocks) 2097151
nofiles(descriptors) unlimited
Verify the same for the Oracle user. Next, you need to increase Oracle user processes to 8192. You can increase the processes for the Oracle user via the “smit†utility on AIX-based servers.
