Содержание
- Ошибка ORA-01034 и ORA-2710: shared memory realm does not exist
- Причина ошибки ORA-01034 и ORA-2710
- Как исправить ошибки ORA-01034 и ORA-2710
- Error 1034 received logging on to the standby — yes another one
- Best Answer
- Answers
- RAC Expdp Error
- Best Answer
- Answers
- oracle db 12.2 impdp issue
- Cause
- Solution
- IMP-00058: ORACLE error 1034 encountered
Здравствуйте, уважаемые коллеги. Хочу поделиться сегодня с вами ситуацией, с которой столкнулся при подключении к базе данных Oracle 12c из стороннего клиентского приложения (архитектура клиент-сервер). При отладке приложения и запуске команды running fnd_nodes cleanup получил ошибку:
При этом я вполне мог подключиться к базе данных и выполнить autoconfig на стороне базы. Но на стороне приложения все также вылетали ошибки и я не смог подключиться к БД из приложения. При этом база данных Oracle запущена и работает штатно.
Честно говоря, я не особо понял причину этой ошибки. Я проверил файлы XML и DBC, файл TNSNAME и listener, но я понять ничего не смог. Все в норме.
Причина ошибки ORA-01034 и ORA-2710
Поколупавшись еще немного в интернете и своих мозгах, я понял эти ошибки связаны с ограниченной сессией к базе данных (db restricted session). Для того, чтобы запустить adstats.sql в приложении, я должен был разрешить ограниченную сессию к ДБ (restricted session). Но я забыл закрыть ее после того, как запустил adstats.sql. Это и вызывало ошибки.
Как исправить ошибки ORA-01034 и ORA-2710
Просто я отключился от БД один раз (закрыл сессию), так как я не мог выяснить причину проблемы сразу в процессе устранения неполадок. После этого эта ошибка исчезла.
Также вы можете выполнить следующую команду, чтобы избежать этой ошибки и без необходимости в закрытии сессии:
Источник
Error 1034 received logging on to the standby — yes another one
Oracle 11.2.0.4 EE on Solaris
I have three (3) Primary databases on three (3) different servers each with a Physical Standby at the backup site.
They have been working very well together for several years.
We had a major power outage at the Primary data center yesterday and now my Primary databases are not sending archive files to the Standby databases.
I am receiving the above error message in the alert log of the Primary.
I am able to ‘tnsping’ from the Primary to the Standby and Standby to Primary in all cases.
I recreated the password files and copied to the Standby servers.
I bounced the Standby databases and restarted MRP.
I am able to ‘connect sys/
@primary as sysdba’ from the Standby.
When I try to do the same from the Primary as ‘connect sys/
@standby as sysdba’ I get ‘ORA-01017: invalid username/password; logon denied’
Any other suggestions are very welcome!!
Best Answer
While reviewing , i saw the parameter you have set on standby and on primary as well. With that parameter there will be no changes/modifications will be accepted until unless you reload the listener after changing in listener.ora file.
I would suggest you to reload or remove the parameter for now to test.
I have asked you for any parameters configured in sqlnet.ora, if any of them available please do paste here.
Please confirm what is the service_name used in Oracle net service of standby? have you reverted ? Because we are following thread on earlier suggestions but not from beginning.
Answers
Did you verified if your standby database is mounted? 1034 Ora error shows your instances was not started.
-bash-4.1$ oerr ora 1034
01034, 00000, «ORACLE not available»
// *Cause: Oracle was not started up. Possible causes include the following:
// — The SGA requires more space than was allocated for it.
// — The operating-system variable pointing to the instance is
// *Action: Refer to accompanying messages for possible causes and correct
// the problem mentioned in the other messages.
// If Oracle has been initialized, then on some operating systems,
// verify that Oracle was linked correctly. See the platform
// specific Oracle documentation.
Thanks for your quick response.
Yes, I bounced the Standby database and restarted MRP. It appears the Standby is operating normally.
When I try to do the same from the Primary as ‘connect sys/
@standby as sysdba’ I get ‘ORA-01017: invalid username/password; logon denied’
If you are not able to connect to standby database as sysdba from primary, it is mostly due to wrong password file. Copy password file from primary to standby and rename as per standby instance name. Check if you are able to connect again. If the issue persists try recreating password file on both instances with orapwd ignorecase=Y option
Thanks again fro your help!
I have already created new password files and copied to the Standby servers. I didn’t use the ‘ignorecase=y’ option because they have been working perfectly until yesterday’s power failure.
My Standby databases have the same instance name as the Primary as is required I thought.
I have bounced the Standby instances and restarted MRP.
Keep the ideas coming!
I am seeing this in the alert.log of the Primary:
I can’t figure out what file or directory is ‘missing’. This has been working for years.
Thanks very much.
I would prefer to check the output from the URL , Then please post output of the primary and standby database output log here.
Thanks for jumping in.
Here is the outpout you requested. I’ve removed a few of the repeating rows to save space.
Источник
RAC Expdp Error
i tried to expdp in RAC 11gr2 2 node database.
Thanks in advance
Best Answer
When you say sqlplus is working how do you connect — expdp uses the same login process so if one works the other should too.
and expdp user/pass (without the @db?)
That might be part of it (hence my question about ORACLE_SID).
Be aware the ‘directory’ is an oracle directory object rather than a directory on the filesystem — so something like
SQL> create directory test as ‘/tmp’;
Answers
It looks just like you have ORACLE_SID set to the wrong value.
Thank you richard for your prompt response
i have checked oratab,
i dont have sys passwd, i could connect to sql plus from $prompt.
i have created directory with ‘test» user, i tried to expdp with test user only,
i assume this is the problem with permissions on directory?
When you say sqlplus is working how do you connect — expdp uses the same login process so if one works the other should too.
and expdp user/pass (without the @db?)
That might be part of it (hence my question about ORACLE_SID).
Be aware the ‘directory’ is an oracle directory object rather than a directory on the filesystem — so something like
SQL> create directory test as ‘/tmp’;
thank you richard
i tried in this way
Thank you Richard
Got it Richard, oracle user doesnt have permission on that directory
That looks like just a missing ‘physical ‘ directory.
select * from dba_directories where directory_name=’BACKUP’;
check this path actually exists on all the nodes in the cluster — adding cluster=N just means it won’t run on more than one instance — however you don’t know which instance that will be — so it may be running on one you dont expect.
Источник
oracle db 12.2 impdp issue
I have a issue with impdp on 12.2.
dp dir is created in pluggable database and permissions are granted.
Can’t find any issue with directory paths.
But im getting below error.
[email protected]####:/backup/expdp$ export ORACLE_SID=racdb1
[email protected]###:/backup/expdp$ impdp system/*******@pdb1 directory=DATA_PUMP_DIR_PDB1 schemas=test dumpfile=test.dmp logfile=test_imp.log;
Import: Release 12.2.0.1.0 — Production on Fri May 18 09:26:21 2018
Copyright (c) 1982, 2017, Oracle and/or its affiliates. All rights reserved.
UDI-01034: operation generated ORACLE error 1034
ORA-01034: ORACLE not available
ORA-27101: shared memory realm does not exist
SVR4 Error: 2: No such file or directory
Additional information: 2503
Additional information: -729422293
UDI-00003: all allowable logon attempts failed
I found below note which seems is the issue,but can someone let me know how to do a peoper impdp in 12c rac env.Anyway of performing without @<db>?
(Doc ID 1317798.1)
Cause
You used the sqlnet identifier (@<db>) while performing export using expdp. On RAC, the connection was routed to another instance where there was not enough permissions on mentioned directory.
Solution
1. Use a local directory as /tmp. The file will then get created in /tmp of another instance.
2. Do not use the sqlnet identifier while performing export on a RAC instance.
Источник
IMP-00058: ORACLE error 1034 encountered
I got an oracle XE 10g on a linux CentOS.
When i want to import my dump into my instance i got a:
IMP-00058: ORACLE error 1034 encountered
ORA-01034: ORACLE not available
ORA-27101: shared memory realm does not exist
Linux Error: 2: No such file or directory
IMP-00005: all allowable logon attempts failed
IMP-00000: Import terminated unsuccessfully
here is the command:
+[[email protected] tmp]$ imp exp_remu_mini.dmp+
Import: Release 10.2.0.1.0 — Production on Mon Sep 7 14:09:08 2009
Copyright (c) 1982, 2005, Oracle. All rights reserved.
I got the same error when using only the imp command:
+[[email protected] tmp]$ imp+
Import: Release 10.2.0.1.0 — Production on Mon Sep 7 14:14:39 2009
Copyright (c) 1982, 2005, Oracle. All rights reserved.
IMP-00058: ORACLE error 1034 encountered
ORA-01034: ORACLE not available
ORA-27101: shared memory realm does not exist
Linux Error: 2: No such file or directory
IMP-00005: all allowable logon attempts failed
IMP-00000: Import terminated unsuccessfully
Here are my env variables:
[[email protected] tmp]$ env |grep ORA
ORACLE_SID=xe
ORACLE_HOME=/usr/lib/oracle/xe/app/oracle/product/10.2.0/server/
Any idea ?
Thanx for ur help
Nicolas
Источник
Hi all,
After upgrading both databases to 11g verson:
The problem is on the standby database, automatic recovery is not working, evenb though is OK in manual mode.
Error Message on Oracle primary alert log (/oracle/dev/saptrace/diag/rdbms/dev/dev/trace)
Error 1034 received logging on to the standby
And in trace file :(/oracle/dev/saptrace/diag/rdbms/dev/dev/trace/dev_arc1.trc for example
OCISessionBegin failed -1
.. Detailed OCI error val is 1034 and errmsg is ‘ORA-01034: ORACLE not available
ORA-27101: shared memory realm does not exist
IBM AIX RISC System/6000 Error: 2: No such file or directory
‘
*** 2012-12-07 14:01:32.856 4320 krsh.c
Error 1034 received logging on to the standby
*** 2012-12-07 14:01:32.856 915 krsu.c
Error 1034 connecting to destination LOG_ARCHIVE_DEST_2 standby host ‘dev_STANDBY’
Error 1034 attaching to destination LOG_ARCHIVE_DEST_2 standby host ‘dev_STANDBY’
*** 2012-12-07 14:01:32.856 4320 krsh.c
PING[ARC2]: Heartbeat failed to connect to standby ‘dev_STANDBY’. Error is 1034.
*** 2012-12-07 14:01:32.856 2957 krsi.c
krsi_dst_fail: dest:2 err:1034 force:0 blast:1
Any hints ?
For now, I am applying the logs manually, but we need to fix the issue.
Environment: Oracle 11.2.0.4 EE on Solaris I have three (3) Primary databases on three (3) different servers each with a Physical Standby at the backup site. They have been working very well together for several years. We had a major power outage at the Primary data center yesterday and now my Primary databases are not sending archive files to the Standby databases. I am receiving the above error message in the alert log of the Primary. I am able to 'tnsping' from the Primary to the Standby and Standby to Primary in all cases. I recreated the password files and copied to the Standby servers. I bounced the Standby databases and restarted MRP. I am able to 'connect sys/<password>#primary as sysdba' from the Standby. When I try to do the same from the Primary as 'connect sys/<password>#standby as sysdba' I get 'ORA-01017: invalid username/password; logon denied' Any other suggestions are very welcome!! -gary
Did you verified if your standby database is mounted? 1034 Ora error shows your instances was not started.-bash-4.1$ oerr ora 103401034, 00000, "ORACLE not available"// *Cause: Oracle was not started up. Possible causes include the following:// - The SGA requires more space than was allocated for it.// - The operating-system variable pointing to the instance is// improperly defined.// *Action: Refer to accompanying messages for possible causes and correct// the problem mentioned in the other messages.// If Oracle has been initialized, then on some operating systems,// verify that Oracle was linked correctly. See the platform// specific Oracle documentation.
Thanks for your quick response. Yes, I bounced the Standby database and restarted MRP. It appears the Standby is operating normally.
SQL> select status from v$instance;
STATUS
------------
MOUNTED
-gary
When I try to do the same from the Primary as 'connect sys/<password>#standby as sysdba' I get 'ORA-01017: invalid username/password; logon denied' If you are not able to connect to standby database as sysdba from primary, it is mostly due to wrong password file. Copy password file from primary to standby and rename as per standby instance name. Check if you are able to connect again. If the issue persists try recreating password file on both instances with orapwd ignorecase=Y option
Thanks again fro your help! I have already created new password files and copied to the Standby servers. I didn't use the 'ignorecase=y' option because they have been working perfectly until yesterday's power failure. My Standby databases have the same instance name as the Primary as is required I thought. I have bounced the Standby instances and restarted MRP. Keep the ideas coming! -gary
I am seeing this in the alert.log of the Primary:
*** 2015-06-08 12:15:23.416
OCISessionBegin failed. Error -1
.. Detailed OCI error val is 1034 and errmsg is 'ORA-01034: ORACLE not available
ORA-27101: shared memory realm does not exist
SVR4 Error: 2: No such file or directory
I can't figure out what file or directory is 'missing'. This has been working for years. Thanks very much. -gary
I would prefer to check the output from the URL , Then please post output of the primary and standby database output log here. Thanks.
Hi Nassyam Thanks for jumping in. Here is the outpout you requested. I've removed a few of the repeating rows to save space. Primary: NAME DISPLAY_VALUE------------------------------ ----------------------------------------------------------------------db_file_name_convert /u01/oradata/APSMDMP1, /u01/oradata/APSMDMP1, /u02/oradata/APSMDMP1, /u02/oradata/APSMDMP1, /u03/oradata/APSMDMP1, /u03/oradata/APSMDMP1, /u04/oradata/APSMDMP1, /u04/oradata/APSMDMP1 db_name APSMDMP1db_unique_name APSMDMP1dg_broker_config_file1 /u01/app/oracle/product/11203/db_1/dbs/dr1APSMDMP1.datdg_broker_config_file2 /u01/app/oracle/product/11203/db_1/dbs/dr2APSMDMP1.datdg_broker_start FALSEfal_clientfal_serverlocal_listenerlog_archive_config DG_CONFIG=(APSMDMP1,APSMDMP1STBY)log_archive_dest_2 SERVICE=APSMDMP1STBY ASYNC VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=APSMDMP1STBY log_archive_dest_state_2 ENABLElog_archive_max_processes 4log_file_name_convert /u01/oradata/APSMDMP1, /u01/oradata/APSMDMP1remote_login_passwordfile EXCLUSIVEstandby_archive_dest ?/dbs/archstandby_file_management AUTO NAME DB_UNIQUE_NAME PROTECTION_MODE DATABASE_R OPEN_MODE SWITCHOVER_STATUS---------- ------------------------------ -------------------- ---------- -------------------- --------------------APSMDMP1 APSMDMP1 MAXIMUM PERFORMANCE PRIMARYREAD WRITE FAILED DESTINATION THREAD# MAX(SEQUENCE#)---------- --------------1 13764 SEVERITY ERROR_CODE timestamp MESSAGE--------------- ---------- -------------------- ------------------------------------------------------------------------------------------Error 1034 08-JUN-2015 11:42:49 PING[ARC0]: Heartbeat failed to connect to standby 'APSMDMP1STBY'. Error is 1034.Error 1034 08-JUN-2015 11:43:52 PING[ARC0]: Heartbeat failed to connect to standby 'APSMDMP1STBY'. Error is 1034.Error 1034 08-JUN-2015 11:44:54 PING[ARC0]: Heartbeat failed to connect to standby 'APSMDMP1STBY'. Error is 1034.Error 1034 08-JUN-2015 11:45:57 PING[ARC0]: Heartbeat failed to connect to standby 'APSMDMP1STBY'. Error is 1034.Error 1034 08-JUN-2015 11:47:02 PING[ARC0]: Heartbeat failed to connect to standby 'APSMDMP1STBY'. Error is 1034.Error 1034 08-JUN-2015 11:48:09 PING[ARC0]: Heartbeat failed to connect to standby 'APSMDMP1STBY'. Error is 1034.Error 1034 08-JUN-2015 11:49:11 PING[ARC0]: Heartbeat failed to connect to standby 'APSMDMP1STBY'. Error is 1034.Error 1034 08-JUN-2015 11:50:15 PING[ARC0]: Heartbeat failed to connect to standby 'APSMDMP1STBY'. Error is 1034.Error 1034 08-JUN-2015 11:51:19 PING[ARC0]: Heartbeat failed to connect to standby 'APSMDMP1STBY'. Error is 1034.Error 1034 08-JUN-2015 11:51:24 FAL[server, ARC3]: Error 1034 creating remote archivelog file 'APSMDMP1STBY'Error 1034 08-JUN-2015 11:57:22 PING[ARC0]: Heartbeat failed to connect to standby 'APSMDMP1STBY'. Error is 1034.Error 1034 08-JUN-2015 11:58:24 PING[ARC0]: Heartbeat failed to connect to standby 'APSMDMP1STBY'. Error is 1034.Error 1034 08-JUN-2015 11:59:27 PING[ARC0]: Heartbeat failed to connect to standby 'APSMDMP1STBY'. Error is 1034.Error 1034 08-JUN-2015 12:00:21 FAL[server, ARC2]: Error 1034 creating remote archivelog file 'APSMDMP1STBY'Error 1034 08-JUN-2015 12:05:30 PING[ARC0]: Heartbeat failed to connect to standby 'APSMDMP1STBY'. Error is 1034.Error 1034 08-JUN-2015 12:06:32 PING[ARC0]: Heartbeat failed to connect to standby 'APSMDMP1STBY'. Error is 1034.Error 1034 08-JUN-2015 12:07:04 FAL[server, ARC2]: Error 1034 creating remote archivelog file 'APSMDMP1STBY'Error 1034 08-JUN-2015 12:12:34 PING[ARC0]: Heartbeat failed to connect to standby 'APSMDMP1STBY'. Error is 1034.Error 1034 08-JUN-2015 12:13:37 PING[ARC0]: Heartbeat failed to connect to standby 'APSMDMP1STBY'. Error is 1034.Error 1034 08-JUN-2015 12:14:40 PING[ARC0]: Heartbeat failed to connect to standby 'APSMDMP1STBY'. Error is 1034.Error 1034 08-JUN-2015 12:15:24 PING[ARC0]: Heartbeat failed to connect to standby 'APSMDMP1STBY'. Error is 1034.Error 1034 08-JUN-2015 12:15:26 FAL[server, ARC2]: Error 1034 creating remote archivelog file 'APSMDMP1STBY'Error 1034 08-JUN-2015 12:15:26 Error 1034 for archive log file 7 to 'APSMDMP1STBY'Error 1034 08-JUN-2015 12:20:44 PING[ARC0]: Heartbeat failed to connect to standby 'APSMDMP1STBY'. Error is 1034.Error 1034 08-JUN-2015 12:21:47 PING[ARC0]: Heartbeat failed to connect to standby 'APSMDMP1STBY'. Error is 1034.Error 1034 08-JUN-2015 12:22:50 PING[ARC0]: Heartbeat failed to connect to standby 'APSMDMP1STBY'. Error is 1034.Error 1034 08-JUN-2015 12:23:54 PING[ARC0]: Heartbeat failed to connect to standby 'APSMDMP1STBY'. Error is 1034.Error 1034 08-JUN-2015 12:24:58 PING[ARC0]: Heartbeat failed to connect to standby 'APSMDMP1STBY'. Error is 1034.Error 1034 08-JUN-2015 12:26:02 PING[ARC0]: Heartbeat failed to connect to standby 'APSMDMP1STBY'. Error is 1034.Error 1034 08-JUN-2015 12:26:27 FAL[server, ARC2]: Error 1034 creating remote archivelog file 'APSMDMP1STBY'Error 1034 08-JUN-2015 12:32:05 PING[ARC0]: Heartbeat failed to connect to standby 'APSMDMP1STBY'. Error is 1034.Error 1034 08-JUN-2015 12:33:15 PING[ARC0]: Heartbeat failed to connect to standby 'APSMDMP1STBY'. Error is 1034.Error 1034 08-JUN-2015 12:34:20 PING[ARC0]: Heartbeat failed to connect to standby 'APSMDMP1STBY'. Error is 1034.Error 1034 08-JUN-2015 12:35:30 PING[ARC0]: Heartbeat failed to connect to standby 'APSMDMP1STBY'. Error is 1034.Error 1034 08-JUN-2015 12:36:34 PING[ARC0]: Heartbeat failed to connect to standby 'APSMDMP1STBY'. Error is 1034.Error 1034 08-JUN-2015 12:37:36 PING[ARC0]: Heartbeat failed to connect to standby 'APSMDMP1STBY'. Error is 1034.Error 1034 08-JUN-2015 12:38:41 PING[ARC0]: Heartbeat failed to connect to standby 'APSMDMP1STBY'. Error is 1034.Error 1034 08-JUN-2015 12:39:45 PING[ARC0]: Heartbeat failed to connect to standby 'APSMDMP1STBY'. Error is 1034.Error 1034 08-JUN-2015 12:40:49 PING[ARC0]: Heartbeat failed to connect to standby 'APSMDMP1STBY'. Error is 1034.Error 1034 08-JUN-2015 12:41:51 PING[ARC0]: Heartbeat failed to connect to standby 'APSMDMP1STBY'. Error is 1034.Error 1034 08-JUN-2015 12:42:54 PING[ARC0]: Heartbeat failed to connect to standby 'APSMDMP1STBY'. Error is 1034.Error 1034 08-JUN-2015 12:44:00 PING[ARC0]: Heartbeat failed to connect to standby 'APSMDMP1STBY'. Error is 1034. ID STATUSDB_MODE TYPE RECOVERY_MODE PROTECTION_MODE SRLs ACTIVE ARCHIVED_SEQ#--- --------- --------------- ---- -------------------- -------------------- ---- ------ ------------- 1 VALIDOPEN ARCH IDLE MAXIMUM PERFORMANCE0 0 13764 2 ERRORUNKNOWN LGWR IDLE MAXIMUM PERFORMANCE0 0 0 NAME Size MBUsed MB------------------------------------------------------------ ---------- ----------/rman 1024000 0 ====================================================================== STANDBY: NAME DISPLAY_VALUE------------------------------ --------------------------------------------------------------------------------------------------------------db_file_name_convert /u01/oradata/APSMDMP1, /u01/oradata/APSMDMP1, /u02/oradata/APSMDMP1, /u02/oradata/APSMDMP1, /u03/oradata/APSMDMP1, /u03/oradata/APSMDMP1, /u04/oradata/APSMDMP1, /u04/oradata/APSMDMP1 db_name APSMDMP1db_unique_name APSMDMP1STBYdg_broker_config_file1 /u01/app/oracle/product/11203/db_1/dbs/dr1APSMDMP1STBY.datdg_broker_config_file2 /u01/app/oracle/product/11203/db_1/dbs/dr2APSMDMP1STBY.datdg_broker_start FALSEfal_client APSMDMP1STBYfal_server APSMDMP1local_listenerlog_archive_config DG_CONFIG=(APSMDMP1,APSMDMP1STBY)log_archive_dest_2 SERVICE=APSMDMP1 ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=APSMDMP1 MAX_CONNECTIONS=2log_archive_dest_state_2 DEFERlog_archive_max_processes 4log_file_name_convert /u01/oradata/APSMDMP1, /u01/oradata/APSMDMP1remote_login_passwordfile EXCLUSIVEstandby_archive_dest ?/dbs/archstandby_file_management AUTO NAME DB_UNIQUE_NAME PROTECTION_MODE DATABASE_ROLE OPEN_MODE---------- ------------------------------ ------------------------- -------------------- --------------------APSMDMP1 APSMDMP1STBY MAXIMUM PERFORMANCE PHYSICAL STANDBYMOUNTED THREAD# MAX(SEQUENCE#)---------- --------------1 13733 PROCESS STATUS THREAD# SEQUENCE#--------- ------------ ---------- ----------ARCH CONNECTED 0 0ARCH CONNECTED 0 0ARCH CONNECTED 0 0ARCH CONNECTED 0 0MRP0 WAIT_FOR_LOG 1 13734 Thread Last Sequence Received Last Sequence Applied Difference---------- ---------------------- --------------------- ----------1 13733 13733 0 NAME VALUE UNIT TIME_COMPUTED DATUM_TIME------------------------------ -------------------- ------------------------------ ------------------------------ ------------------------------transport lag day(2) to second(0) interval 06/08/2015 12:45:26apply lag day(2) to second(0) interval 06/08/2015 12:45:26apply finish time day(2) to second(3) interval 06/08/2015 12:45:26estimated startup time 10 second 06/08/2015 12:45:26 NAME Size MBUsed MB------------------------------------------------------------ ---------- ----------/rman 204800 0 =============== I appreciate the help!! -gary
I am able to 'connect sys/<password>#primary as sysdba' from the Standby.
When I try to do the same from the Primary as 'connect sys/<password>#standby as sysdba' I get 'ORA-01017: invalid username/password; logon denied'
So its clear that there is no issues in connecting from standby to primary, but only issue is with connecting to standby database. As i see there is no issue from configuration as per the log you have posted. However i want to look at them closely. Before that i want you to run the below commands on primary and standby for password file.
$md5sum orapw$ORACLE_SID
$ls -ltr orapw$ORACLE_SID
So these commands you need to run both on primary and standby and share the results.
Thanks very much for your help!!! Here are the results: I didn't have the 'md5sum' command but I found the 'digest' command for Solaris: 'digest -a md5 -v orapwAPSMDMP1 b628acdd96a84e569d1a8ab4c64a31ca - Primaryb628acdd96a84e569d1a8ab4c64a31ca - Standby Primary: ls -ltr orapwAPSMDMP1-rw-r----- 1 oracle oinstall 2048 Jun 8 10:21 orapwAPSMDMP1 Standby: ls -ltr orapwAPSMDMP1-rw-r----- 1 oracle oinstall 2048 Jun 8 10:24 orapwAPSMDMP1 -gary
b628acdd96a84e569d1a8ab4c64a31ca - Primary
b628acdd96a84e569d1a8ab4c64a31ca - Standby
Password file looks good for me and no issues around. I would ask you, whether there are any changes in port of listener on standby ? might be it's not updated in primary TNS?Are you able to connect standby to standby?(not from primary to standby)Any thing have you configured in sqlnet.ora? share the outputCan you please share the alert log of standby after you do stop and start MRP? basically i need fresh logs. Thanks.
Nassyam I have made no changes to the listener configuration, passwords, ports, etc. This environment was working fine last week but is now having trouble after the power outage in the data center yesterday. I'm trying to figure out how the 2 events are related, if they are. It just seems an odd coincidence. I have added the Standby entry to the Standby TNSNAMES.ORA file and attempted a login on the Standby as follows: SQL> conn sys/<password>#apsmdmp1stby as sysdbaERROR:ORA-01017: invalid username/password; logon deniedHere is the Standby alert log output from the stop and start of MRP: Mon Jun 08 14:25:45 2015alter database recover managed standby database cancelMon Jun 08 14:25:45 2015MRP0: Background Media Recovery cancelled with status 16037Errors in file /u01/app/oracle/diag/rdbms/apsmdmp1stby/APSMDMP1/trace/APSMDMP1_pr00_29640.trc:ORA-16037: user requested cancel of managed recovery operationManaged Standby Recovery not using Real Time ApplyRecovery interrupted!Mon Jun 08 14:25:45 2015MRP0: Background Media Recovery process shutdown (APSMDMP1)Managed Standby Recovery Canceled (APSMDMP1)Completed: alter database recover managed standby database cancelMon Jun 08 14:26:20 2015alter database recover managed standby database using current logfile disconnectAttempt to start background Managed Standby Recovery process (APSMDMP1)Mon Jun 08 14:26:20 2015MRP0 started with pid=25, OS id=29783MRP0: Background Managed Standby Recovery process started (APSMDMP1)started logmerger processMon Jun 08 14:26:25 2015Managed Standby Recovery starting Real Time ApplyParallel Media Recovery started with 32 slavesWaiting for all non-current ORLs to be archived...All non-current ORLs have been archived.Media Recovery Waiting for thread 1 sequence 13734Completed: alter database recover managed standby database using current logfile disconnect Thanks very much!! -gary
hello, why do you not try, renaming standby passwd file from orapwAPSMDMP1 to orapwdAPSMDMP1STBY.ora ? Regards
Thanks for your feedback. According to the docs, the default password file name uses the ORACLE_SID to create a file like 'orapwORACLE_SID'. The SID for both databases is APSMDMP1. -gary
oh!, sorry. I like to use different ORACLE_SID for primary and standby instances, usually i configure ORACLE_SID identical instance_name and identical to DB_UNIQUE_NAME, but it is only a personal choice ( i think that it is better for clarify...). If you configure identical ORACLE_SID for both primary and standby, sure you will have a good reason of it. A basic question: is the SYS passwords identical for primary and standby and are you changed it when recreated password file?be aware of parameter SEC_CASE_SENSITIVE_LOGON in primary and standby. Your primary site has been restarted so, are you sure that init.ora or spfile.ora parameters are the same? I guess that REDO_TRANSPORT_USER is not set. (if it set see MOS 1416595.1) Another (stupid) question: are oracle.oinstall oracle software owner and group in both machines?are orapwd$ORACLE_SID in correct $ORACLE_HOME/dbs ?i ask it because i usually work with differents operating system users for differents databases. ...Regards
Related
Standby not in SYNC WRT Primary
Hi all, I had configured DG in my machine for practice purpose.(11.2.0.1.0) on my windows laptopOnce it was running fine (syncing) i tried switchover which also worked. I wanted to practice upgradation (11.2.0.4.0 to 12.1.0.1) which i did & needed a few more checks so paused it for a while & started my DG setup. DG setup Originally Primary => ORCLStandby => DUPORCL after switchoverPrimary => DUPORCLStandby => ORCL I started DUPORCL 1st & then ORCLwhen i checked thearchive log list; the sequence numbers dint match, later i found tnsping was not working so made the necessary modifications & tnsping is working fine. still there is issue of sequence is not matching... #ORCL / physical standby SQL> select message from v$dataguard_status; MESSAGE-------------------------------------------------------------------------------- ARC0: Archival startedARC1: Archival startedARC1: Becoming the 'no FAL' ARCHARC1: Becoming the 'no SRL' ARCHARC2: Archival startedARC3: Archival startedARC4: Archival startedARC4: Becoming the heartbeat ARCHARC5: Archival startedARC6: Archival startedARC7: Archival started MESSAGE-------------------------------------------------------------------------------- ARC8: Archival startedARC9: Archival startedARCa: Archival startedARCb: Archival startedARCc: Archival startedARCd: Archival startedARCe: Archival startedARCf: Archival startedARCg: Archival startedARCh: Archival startedARCi: Archival started MESSAGE-------------------------------------------------------------------------------- ARCj: Archival startedARCk: Archival startedARCl: Archival startedARCm: Archival startedARCn: Archival startedARCo: Archival startedARCp: Archival startedARCq: Archival startedARCr: Archival startedARCs: Archival startedARCt: Archival started MESSAGE-------------------------------------------------------------------------------- Error 3113 received logging on to the standbyFAL[client, ARC2]: Error 3113 connecting to DUPORCL for fetching gap sequenceAttempt to start background Managed Standby Recovery processMRP0: Background Managed Standby Recovery process startedManaged Standby Recovery not using Real Time ApplyMedia Recovery Waiting for thread 1 sequence 131Error 3113 received logging on to the standbyFAL[client, USER]: Error 3113 connecting to DUPORCL for fetching gap sequence 41 rows selected. #DUPORCL / Primary SQL> select severity, error_code, to_char(timestamp,'DD-MON-YYYY HH24:MI:SS'), message from v$dataguard_status where dest_id=2; SEVERITY ERROR_CODE TO_CHAR(TIMESTAMP,'D------------- ---------- --------------------MESSAGE-------------------------------------------------------------------------------- Error 12541 06-OCT-2015 21:26:13PING[ARC1]: Heartbeat failed to connect to standby 'orcl'. Error is 12541. Error 12541 06-OCT-2015 21:26:15FAL[server, ARC3]: Error 12541 creating remote archivelog file 'orcl' Error 12541 06-OCT-2015 21:26:16Error 12541 for archive log file 3 to 'orcl' SEVERITY ERROR_CODE TO_CHAR(TIMESTAMP,'D------------- ---------- --------------------MESSAGE-------------------------------------------------------------------------------- Error 12541 06-OCT-2015 21:27:12PING[ARC1]: Heartbeat failed to connect to standby 'orcl'. Error is 12541. Error 12541 06-OCT-2015 21:32:45PING[ARC1]: Heartbeat failed to connect to standby 'orcl'. Error is 12541. Error 12541 06-OCT-2015 21:38:13PING[ARC1]: Heartbeat failed to connect to standby 'orcl'. Error is 12541. SEVERITY ERROR_CODE TO_CHAR(TIMESTAMP,'D------------- ---------- --------------------MESSAGE-------------------------------------------------------------------------------- Error 3113 06-OCT-2015 21:44:20PING[ARC1]: Heartbeat failed to connect to standby 'orcl'. Error is 3113. Error 3113 06-OCT-2015 21:50:25PING[ARC1]: Heartbeat failed to connect to standby 'orcl'. Error is 3113. Error 3113 06-OCT-2015 21:55:31PING[ARC1]: Heartbeat failed to connect to standby 'orcl'. Error is 3113. SEVERITY ERROR_CODE TO_CHAR(TIMESTAMP,'D------------- ---------- --------------------MESSAGE-------------------------------------------------------------------------------- Error 3113 06-OCT-2015 22:00:36PING[ARC1]: Heartbeat failed to connect to standby 'orcl'. Error is 3113. Error 3113 06-OCT-2015 22:05:46PING[ARC1]: Heartbeat failed to connect to standby 'orcl'. Error is 3113. Error 1034 06-OCT-2015 22:10:47PING[ARC1]: Heartbeat failed to connect to standby 'orcl'. Error is 1034. SEVERITY ERROR_CODE TO_CHAR(TIMESTAMP,'D------------- ---------- --------------------MESSAGE-------------------------------------------------------------------------------- Error 1034 07-OCT-2015 06:48:29PING[ARC1]: Heartbeat failed to connect to standby 'orcl'. Error is 1034. Error 3113 07-OCT-2015 06:53:42PING[ARC1]: Heartbeat failed to connect to standby 'orcl'. Error is 3113. Error 3113 07-OCT-2015 06:59:47PING[ARC1]: Heartbeat failed to connect to standby 'orcl'. Error is 3113. SEVERITY ERROR_CODE TO_CHAR(TIMESTAMP,'D------------- ---------- --------------------MESSAGE-------------------------------------------------------------------------------- Error 3113 07-OCT-2015 07:05:50PING[ARC1]: Heartbeat failed to connect to standby 'orcl'. Error is 3113. Error 3113 07-OCT-2015 07:11:54PING[ARC1]: Heartbeat failed to connect to standby 'orcl'. Error is 3113. Error 3113 07-OCT-2015 07:17:57PING[ARC1]: Heartbeat failed to connect to standby 'orcl'. Error is 3113. SEVERITY ERROR_CODE TO_CHAR(TIMESTAMP,'D------------- ---------- --------------------MESSAGE-------------------------------------------------------------------------------- Error 3113 07-OCT-2015 07:23:02PING[ARC1]: Heartbeat failed to connect to standby 'orcl'. Error is 3113. Error 3113 07-OCT-2015 07:29:04PING[ARC1]: Heartbeat failed to connect to standby 'orcl'. Error is 3113. Error 3113 07-OCT-2015 07:34:11PING[ARC1]: Heartbeat failed to connect to standby 'orcl'. Error is 3113. SEVERITY ERROR_CODE TO_CHAR(TIMESTAMP,'D------------- ---------- --------------------MESSAGE-------------------------------------------------------------------------------- Error 3113 07-OCT-2015 07:40:14PING[ARC1]: Heartbeat failed to connect to standby 'orcl'. Error is 3113. Error 3113 07-OCT-2015 07:46:19PING[ARC1]: Heartbeat failed to connect to standby 'orcl'. Error is 3113. Error 3113 07-OCT-2015 07:52:23PING[ARC1]: Heartbeat failed to connect to standby 'orcl'. Error is 3113. 24 rows selected. Not sure why standby is not reachable... #ORCLSQL> show parameter fal NAME TYPE VALUE------------------------------------ ----------- ------------------------------fal_client string ORCLfal_server string DUPORCLSQL> show parameter log_archive_dest_2 NAME TYPE VALUE------------------------------------ ----------- ------------------------------log_archive_dest_2 string SERVICE=DUPORCL LGWR ASYNC VAL ID_FOR=(ONLINE_LOGFILES,PRIMAR Y_ROLE) DB_UNIQUE_NAME=DUPORCLlog_archive_dest_20 stringlog_archive_dest_21 string # DUPORCL SQL> show parameter fal NAME TYPE VALUE------------------------------------ ----------- ---------------------------fal_client string duporclfal_server string orclSQL> show parameter log_archive_dest_2 NAME TYPE VALUE------------------------------------ ----------- ------------------------------log_archive_dest_2 string service=orcl ASYNC valid_for=( ONLINE_LOGFILE,PRIMARY_ROLE) d b_unique_name=orcllog_archive_dest_20 string I am suspecting is it something to do with switchover?Please guide me on this. Mohib
I wanted to practice upgradation (11.2.0.4.0 to 12.1.0.1) which i did & needed a few more checks so paused it for a while & started my DG setup. Have you performed upgrade on primary or it got paused ? If you have performed then please copy the latest orapwd file to standby, since it may be not be compatiable with 12c format.From 12c the format gets modified, so you need to re-sync with DR. - Pavan Kumar N
Hi Pavan, The DB got upgraded to 12c (i was able to open the upgraded DB & cross verified data in a schema). - DG is on 11.2.0.1 I have 3 versions of Oracle running1) 11.2.0.1 (2db's ie; DG) 2) 11.2.0.4 (DB)3) 12.1.0.1 (DB) I installed & created DB in 11.2.0.4 & upgraded it to 12.1.0.1.
I have 3 versions of Oracle running 1) 11.2.0.1 (2db's ie; DG) 2) 11.2.0.4 (DB) 3) 12.1.0.1 (DB) 1. then what is the version of DG ? which you stated or provided error information above.2. what is the version of primary then of t hat respective DR ? - Pavan Kumar N
Before doing a switchover did you check if you were in sync? As part of the upgrade did you update the Net80 setting on both ends for the new Oracle home? Best Regards mseberg
Hi, DG is setup on 11.2.0.1.0 version.Above error DB version is 11.2.0.1.0Both primary & standby are on 11.2.0.1.0.
Hi, 1. Can you test tnsping vice versa2. Can you login using sysdba vice versa using tns connection string3. If you verify and resolve above two the DG works fine. To work above two make sure you have orapwd and correct password in sync and listeners up and running. Make sure you are using correct tns service and log_Arch --DUPORCLCheck for any firewall ports got enabled -- just in-case - Pavan Kumar N
3113. Check your password on the Standby. In Oracle 11 you can no longer just create a new password file for the physical standby database. You musts always copy the primary database password file to all physical standby databases whenever a privileged user's password is changed. Best Regards mseberg
Hi, Not getting the question clearly .. what is DG version, why do you compare with other three version of your database. Thanks,
Hi, Sorry for the delay... #Standby SQL> select name,db_unique_name,open_mode,database_role,switchover_status from$database; NAME DB_UNIQUE_NAME OPEN_MODE DATABASE_ROLE--------- ------------------------------ -------------------- ----------------SWITCHOVER_STATUS--------------------ORCL ORCL MOUNTED PHYSICAL STANDBYNOT ALLOWED SQL> exitDisconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 6bit ProductionWith the Partitioning, OLAP, Data Mining and Real Application Testing options C:Userssyed>tnsping duporcl TNS Ping Utility for 64-bit Windows: Version 12.1.0.1.0 - Production on 13-OCT-015 08:01:26 Copyright (c) 1997, 2013, Oracle. All rights reserved. Used parameter files:E:12101_dbappproduct12.1.0dbhome_1networkadminsqlnet.ora Used TNSNAMES adapter to resolve the aliasAttempting to contact (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = user)(PRT = 1521)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = duporcl)))OK (10 msec) C:Userssyed>sqlplus sys/oracle#duporcl as sysdba SQL*Plus: Release 12.1.0.1.0 Production on Tue Oct 13 08:02:07 2015 Copyright (c) 1982, 2013, Oracle. All rights reserved. Connected to:Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit ProductionWith the Partitioning, OLAP, Data Mining and Real Application Testing optionsSQL> archive log list;Database log mode Archive ModeAutomatic archival EnabledArchive destination USE_DB_RECOVERY_FILE_DESTOldest online log sequence 129Next log sequence to archive 0Current log sequence 131 #Primary SQL> select name,db_unique_name,open_mode,database_role,switchover_status from v$database; NAME DB_UNIQUE_NAME OPEN_MODE DATABASE_ROLE--------- ------------------------------ -------------------- ----------------SWITCHOVER_STATUS--------------------ORCL duporcl READ WRITE PRIMARYFAILED DESTINATION SQL> exitDisconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit ProductionWith the Partitioning, OLAP, Data Mining and Real Application Testing options C:Userssyed>tnsping orcl TNS Ping Utility for 64-bit Windows: Version 12.1.0.1.0 - Production on 13-OCT-2015 08:01:30 Copyright (c) 1997, 2013, Oracle. All rights reserved. Used parameter files:E:12101_dbappproduct12.1.0dbhome_1networkadminsqlnet.ora Used TNSNAMES adapter to resolve the aliasAttempting to contact (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = user)(PORT = 1521)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = orcl)))OK (10 msec) C:Userssyed>sqlplus sys/oracle#orcl as sysdba SQL*Plus: Release 12.1.0.1.0 Production on Tue Oct 13 08:02:09 2015 Copyright (c) 1982, 2013, Oracle. All rights reserved. Connected to:Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit ProductionWith the Partitioning, OLAP, Data Mining and Real Application Testing optionsSQL> archive log list;Database log mode Archive ModeAutomatic archival EnabledArchive destination USE_DB_RECOVERY_FILE_DESTOldest online log sequence 142Next log sequence to archive 144Current log sequence 144 the tnsping & sqlplus as sysdba are fine... yet the archives r not being applied..... **************************************************************************also i ve this in alert/trace of orcl (standby) db Trace file e:appsyeddiagrdbmsorclorcltraceorcl_arcg_960.trcOracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit ProductionWith the Partitioning, OLAP, Data Mining and Real Application Testing optionsWindows NT Version V6.2 CPU : 4 - type 8664, 2 Physical CoresProcess Affinity : 0x0x0000000000000000Memory (Avail/Total): Ph:935M/3994M, Ph+PgF:3092M/8090M Instance name: orclRedo thread mounted by this instance: 1Oracle process number: 37Windows thread id: 960, image: ORACLE.EXE (ARCG) *** 2015-10-13 08:10:54.776*** SESSION ID:(69.1) 2015-10-13 08:10:54.776*** CLIENT ID:() 2015-10-13 08:10:54.776*** SERVICE NAME:() 2015-10-13 08:10:54.776*** MODULE NAME:() 2015-10-13 08:10:54.776*** ACTION NAME:() 2015-10-13 08:10:54.776 Redo shipping client performing standby login *** 2015-10-13 08:10:58.458OCISessionBegin failed. Error -1.. Detailed OCI error val is 3113 and errmsg is 'ORA-03113: end-of-file on communication channel' *** 2015-10-13 08:11:00.069OCISessionBegin failed. Error -1.. Detailed OCI error val is 3113 and errmsg is 'ORA-03113: end-of-file on communication channel' *** 2015-10-13 08:11:01.540OCISessionBegin failed -1.. Detailed OCI error val is 3113 and errmsg is 'ORA-03113: end-of-file on communication channel'*** 2015-10-13 08:11:01.555 4132 krsh.cError 3113 received logging on to the standby*** 2015-10-13 08:11:01.565 4132 krsh.cFAL[client, ARCg]: Error 3113 connecting to DUPORCL for fetching gap sequenceORA-03113: end-of-file on communication channelORA-03113: end-of-file on communication channel
RFS porcess is stopped
Dear All, Till yesterday my physical dr was in sync and all of sudden this morning i have found 1000 archive gap between my primary and standby. I have applied incremental backup ,i have also replaced old standby controlfile with latest one and tried to put the standby database in recovery mode , but the RFS process is not starting. Following are the required details for the same .. SQL> select banner from v$version; BANNER ---------------------------------------------------------------- Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - Prod PL/SQL Release 10.2.0.4.0 - Production CORE 10.2.0.4.0 Production TNS for 32-bit Windows: Version 10.2.0.4.0 - Production NLSRTL Version 10.2.0.4.0 - Production SQL> select process,status from v$managed_standby; PROCESS STATUS --------- ------------ ARCH CONNECTED ARCH CONNECTED MRP0 WAIT_FOR_GAP SQL> select message from v$dataguard_Status; MESSAGE -------------------------------------------------------------------------------- ARC0: Archival started ARC1: Archival started ARC0: Becoming the 'no FAL' ARCH ARC0: Becoming the 'no SRL' ARCH ARC1: Becoming the heartbeat ARCH Managed Standby Recovery not using Real Time Apply Attempt to start background Managed Standby Recovery process MRP0: Background Managed Standby Recovery process started Managed Standby Recovery not using Real Time Apply Media Recovery Waiting for thread 1 sequence 461642 Fetching gap sequence in thread 1, gap sequence 461642-461679 MESSAGE -------------------------------------------------------------------------------- FAL[client]: Failed to request gap sequence GAP - thread 1 sequence 461642-461679 DBID 2578507424 branch 709654561 FAL[client]: All defined FAL servers have been attempted. Alter log :- Completed: alter database recover managed standby database disconnect from session Wed May 04 13:18:18 2011 FAL[client]: Failed to request gap sequence GAP - thread 1 sequence 461642-461679 DBID 2578507424 branch 709654561 FAL[client]: All defined FAL servers have been attempted. ------------------------------------------------------------- Check that the CONTROL_FILE_RECORD_KEEP_TIME initialization parameter is defined to a value that is sufficiently large enough to maintain adequate log switch information to resolve archivelog gaps. ------------------------------------------------------------- Wed May 04 13:28:52 2011 db_recovery_file_dest_size of 2048 MB is 0.00% used. This is a user-specified limit on the amount of space that will be used by this database for recovery-related files, and does not reflect the amount of space available in the underlying filesystem or ASM diskgroup. mrpo Process:- Redo shipping client performing standby login *** 2011-05-04 13:16:44.162 66535 kcrr.c Logged on to standby successfully Client logon and security negotiation successful! *** 2011-05-04 13:17:15.486 Redo shipping client performing standby login *** 2011-05-04 13:17:15.549 66535 kcrr.c Logged on to standby successfully Client logon and security negotiation successful! *** 2011-05-04 13:17:46.905 Redo shipping client performing standby login *** 2011-05-04 13:17:46.967 66535 kcrr.c Logged on to standby successfully Client logon and security negotiation successful! *** 2011-05-04 13:18:18.245 ----------------------------------------------------------- Check that the CONTROL_FILE_RECORD_KEEP_TIME initialization parameter is defined to a value that is sufficiently large enough to maintain adequate log switch information to resolve archivelog gaps. ----------------------------------------------------------- udump trace output: *** 2011-05-04 13:14:11.672 *** ACTION NAME:() 2011-05-04 13:14:11.500 *** MODULE NAME:(sqlplus.exe) 2011-05-04 13:14:11.500 *** SERVICE NAME:() 2011-05-04 13:14:11.500 *** SESSION ID:(873.1) 2011-05-04 13:14:11.500 tkcrrsarc: (WARN) Failed to find ARCH for message (message:0x4) tkcrrpa: (WARN) Failed initial attempt to send ARCH message (message:0x4) *** 2011-05-04 13:14:23.574 *** 2011-05-04 13:14:23.574 62692 kcrr.c Managed Standby Recovery not using Real Time Apply Recovery target incarnation = 2, activation ID = 0 Influx buffer limit = 80419 (50% x 160839) Successfully allocated 3 recovery slaves Using 364 overflow buffers per recovery slave Start recovery at thread 1 ckpt scn 4075771372 logseq 461642 block 35812 *** 2011-05-04 13:14:29.939 Media Recovery add redo thread 1 *** 2011-05-04 13:14:35.618 Media Recovery drop redo thread 1 *** 2011-05-04 13:15:04.212 *** 2011-05-04 13:15:04.212 2289 krsm.c Managed Recovery: THROUGH NEXT SWITCHOVER posted. *** 2011-05-04 13:15:04.228 1118 krsm.c Managed Recovery: DISCONNECT posted. *** 2011-05-04 13:15:04.228 1118 krsm.c Managed Recovery: Startup posted.
Hi, You should check the primary alert log and also run "select message from v$dataguard_Status;" on the primary to find the cause of this. on primary: log_archive_dest_x may be changed log_archive_dest_state_x may be deferred tns entry pointing the standby may be changed etc.
I have checked the command on Primary and received following message :- Primary>select message from v$dataguard_status; MESSAGE ------------------------------------------------------------------------------ Error 12170 received logging on to the standby PING[ARC0]: Heartbeat failed to connect to standby 'DR1BSL'. Error is 12170. Error 12170 received logging on to the standby FAL[server, ARC0]: Error 12170 creating remote archivelog file 'DR1BSL' Error 12170 received logging on to the standby FAL[server, ARC0]: Error 12170 creating remote archivelog file 'DR1BSL' Error 12170 received logging on to the standby FAL[server, ARC0]: Error 12170 creating remote archivelog file 'DR1BSL' Error 12170 received logging on to the standby FAL[server, ARC0]: Error 12170 creating remote archivelog file 'DR1BSL' Error 12170 received logging on to the standby PING[ARC0]: Heartbeat failed to connect to standby 'DR1BSL'. Error is 12170. Error 12170 received logging on to the standby PING[ARC0]: Heartbeat failed to connect to standby 'DR1BSL'. Error is 12170.
This is a password issue. Have you recently changed your sys password on primary? If yes, you should copy the new password file to standby or create a new one with this command: orapwd file=$ORACLE_HOME/dbs/orapwSID password=newpassword;
Dear All, The issue is now resolved as the issue was from firewall at my dr end. It was actually blocking 1521 port from my Primary end. When i did telnet for 1521 port from Primary , it did not work. Once the fire wall is disabled , the issue is resolved as i can now telnet the 1521 port also getting connection of dr from Primary. Thanks
Dear All, I am using oracle 10g dataguard version: 10.2.0 what i am wanted oracle logs file shifted from Primary database to standby database is there any software avalible once log file shifted to standby database then will alert to you the file has been transfferd to the standby database, if the file will not scuessfull transffer to the standby database also give alert to us. Thanks Naveed
Enterprise Manager. Larry
Heartbeat failed to connect to standby Error is 1031
I getting an error in LogTransportService PING[ARC0]: Heartbeat failed to connect to standby . Error is 1031. Kindly help me
TrustreArun wrote: I getting an error in LogTransportService PING[ARC0]: Heartbeat failed to connect to standby . Error is 1031.What is your version? Are you using DataGuard Broker? From where you trying to connect- From primary to standby? You trying to connect with Oracle Net service or from the same server? Are you using correct password? Lot of information missing from you, Please provide all the information. 01031, 00000, "insufficient privileges" // *Cause: An attempt was made to change the current username or password // without the appropriate privilege. This error also occurs if // attempting to install a database without the necessary operating // system privileges. // When Trusted Oracle is configure in DBMS MAC, this error may occur // if the user was granted the necessary privilege at a higher label // than the current login. // *Action: Ask the database administrator to perform the operation or grant // the required privileges. // For Trusted Oracle users getting this error although granted the // the appropriate privilege at a higher label, ask the database // administrator to regrant the privilege at the appropriate label.
DB Version: Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production Not using data guard broker I checked V$dataguard _status from primary I didn't change my password , it was fine on last day
Until you can do the following: sqlplus sys/password#Standby as sysdba (from the primary system) and sqlplus sys/password#primary as sysdba (from the standby system) You will not be able to ship redo. Would also check ORACLE_SID, SERVICE_NAME in listener.ora and tnsnames.ora make sure you don't have a CASE issue ( lower or upper) Best Regards mseberg
TrustreArun wrote: DB Version: Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production Not using data guard broker I checked V$dataguard _status from primary I didn't change my password , it was fine on last dayHope you trying to connect with "SYS" user, From primary database connect to the standby database as $sqlplus sys/****#standby as sysdba From standby database connect to the primary database as $sqlplus sys/****#primary as sysdba If you are able to connect above both, then i dont think there is any issues, You can do troubleshoot as From primary 1) SQL> alter system set log_archive_dest_state_2='defer'; 2) SQL> alter system set log_archive_dest_state_2='enable'; 3) SQL> alter system switch logfile; -- You can do 2-3 or even more 4) Now monitor the alert logs from primary and standby databases and post if any errors. Also post SQL> select error_code, message,timestamp from v$dataguard_status where dest_id=2;
details of v$dataguard_status 1,031 PING[ARC0]: Heartbeat failed to connect to standby 'STDBY'. Error is 1031. 1,031 PING[ARC0]: Heartbeat failed to connect to standby 'STDBY'. Error is 1031. 1,031 PING[ARC0]: Heartbeat failed to connect to standby 'STDBY'. Error is 1031. 1,031 PING[ARC0]: Heartbeat failed to connect to standby 'STDBY'. Error is 1031. 1,031 PING[ARC0]: Heartbeat failed to connect to standby 'STDBY'. Error is 1031. 1,031 PING[ARC0]: Heartbeat failed to connect to standby 'STDBY'. Error is 1031. 1,031 PING[ARC0]: Heartbeat failed to connect to standby 'STDBY'. Error is 1031. 1,031 PING[ARC0]: Heartbeat failed to connect to standby 'STDBY'. Error is 1031. 1,031 PING[ARC0]: Heartbeat failed to connect to standby 'STDBY'. Error is 1031. 1,031 PING[ARC0]: Heartbeat failed to connect to standby 'STDBY'. Error is 1031. 1,031 PING[ARC0]: Heartbeat failed to connect to standby 'STDBY'. Error is 1031. 1,031 PING[ARC0]: Heartbeat failed to connect to standby 'STDBY'. Error is 1031. 1,031 PING[ARC0]: Heartbeat failed to connect to standby 'STDBY'. Error is 1031. 1,031 PING[ARC0]: Heartbeat failed to connect to standby 'STDBY'. Error is 1031. 1,031 PING[ARC0]: Heartbeat failed to connect to standby 'STDBY'. Error is 1031. 1,031 PING[ARC0]: Heartbeat failed to connect to standby 'STDBY'. Error is 1031. 1,031 PING[ARC0]: Heartbeat failed to connect to standby 'STDBY'. Error is 1031. 1,031 PING[ARC0]: Heartbeat failed to connect to standby 'STDBY'. Error is 1031. 1,031 PING[ARC0]: Heartbeat failed to connect to standby 'STDBY'. Error is 1031. 1,031 PING[ARC0]: Heartbeat failed to connect to standby 'STDBY'. Error is 1031.
Have you read carefully in my previous posts what i have requested? I asked you to do some troubleshoot and to post logs, The information you provided is not sufficient to go ahead. Read Again....
I have encountered similar issue before. the solutions provided above should work.
in my case, the password file (orapw{SID}) on standby was overwritten.
I just copied the password file from primary to standby, renaming to correct filename. This resolved my issue. Log shipping has resumed.
archives on standby not applying
OS-windows 2003Oracle version---Oracle 10gr1 i have configured all as per document but archives not shipping to standbyEven on >select sequence# from v$archived_log on standby giving no rows below is the status primary output select message from v$DATAGUARD_STATUS MESSAGE -------------------------------------------------------------------------------- Error 12545 received logging on to the standby PING[ARC1]: Heartbeat failed to connect to standby 'PROD2'. Error is 12545. Error 12545 received logging on to the standby PING[ARC1]: Heartbeat failed to connect to standby 'PROD2'. Error is 12545. Error 1034 received logging on to the standby PING[ARC1]: Heartbeat failed to connect to standby 'PROD2'. Error is 1034. Error 1034 received logging on to the standby PING[ARC1]: Heartbeat failed to connect to standby 'PROD2'. Error is 1034. Error 1034 received logging on to the standby PING[ARC1]: Heartbeat failed to connect to standby 'PROD2'. Error is 1034. Error 1034 received logging on to the standby MESSAGE -------------------------------------------------------------------------------- PING[ARC1]: Heartbeat failed to connect to standby 'PROD2'. Error is 1034. Error 1034 received logging on to the standby PING[ARC1]: Heartbeat failed to connect to standby 'PROD2'. Error is 1034. Error 1034 received logging on to the standby PING[ARC1]: Heartbeat failed to connect to standby 'PROD2'. Error is 1034. Error 1034 received logging on to the standby PING[ARC1]: Heartbeat failed to connect to standby 'PROD2'. Error is 1034. Error 1034 received logging on to the standby PING[ARC1]: Heartbeat failed to connect to standby 'PROD2'. Error is 1034. Error 1034 received logging on to the standby PING[ARC1]: Heartbeat failed to connect to standby 'PROD2'. Error is 1034. MESSAGE -------------------------------------------------------------------------------- PING[ARC1]: Heartbeat failed to connect to standby 'PROD2'. Error is 16047.output of standby SQL> select message from v$DATAGUARD_STATUS; MESSAGE ----------------------------------------------------- ARC0: Archival started ARC1: Archival started ARC0: Becoming the 'no FAL' ARCH ARC0: Becoming the 'no SRL' ARCH ARC1: Becoming the heartbeat ARCH Media Recovery Start: Managed Standby Recovery Managed Standby Recovery not using Real Time Apply Media Recovery Waiting for thread 1 sequence 11634 Managed Standby Recovery Canceled 9 rows selected.
It does not appear that Primary DB can connect to Standby DB [oracle#localhost ~]$ oerr ora 1254512545, 00000, "Connect failed because target host or object does not exist"// *Cause: The address specified is not valid, or the program being // connected to does not exist.// *Action: Ensure the ADDRESS parameters have been entered correctly; the// most likely incorrect parameter is the node name. Ensure that the // executable for the server exists (perhaps "oracle" is missing.)// If the protocol is TCP/IP, edit the TNSNAMES.ORA file to change the// host name to a numeric IP address and try again.
1. Do from primary host, to see if you able to connect to standby host tnsping STANDBYNAME specified in archive_dest 2. make sure password file is the same as in primary3. disable/enable archive dest on primary. restart standby RegardsEd
Hi, Check the parameter setting LOG_ARCHIVE_CONFIG on both the site and also confirm that you are able to successfully connect from Primary site to Standby. ThanksRajeev
PING[ARC1]: Heartbeat failed to connect to standby ‘stby_crmsdb’. Error is 16058
Hi Please dont assume as duplicate PING[ARC2]: Heartbeat failed to connect to standby 'Already i asked question related to alert.log and also marked as answered. >> This is new Just i am verifying basic commands for DR. I surprised and also much confused Primary and Standby is in SYNC. Archives are shipping and also applied on standby but i am getting ' PING[ARC1]: Heartbeat failed to connect to standby 'stby_crmsdb'. Error is 16058.' in primary database. >> On primary SYS> select message from v$dataguard_status where dest_id = 2; MESSAGE ------------------------------------------------------------------------------------------------------------------------ LNS: Attempting destination LOG_ARCHIVE_DEST_2 network reconnect (3113) LNS: Destination LOG_ARCHIVE_DEST_2 network reconnect abandoned Error 3113 for archive log file 1 to 'stby_crmsdb' PING[ARC1]: Heartbeat failed to connect to standby 'stby_crmsdb'. Error is 16058. PING[ARC1]: Heartbeat failed to connect to standby 'stby_crmsdb'. Error is 16058. PING[ARC1]: Heartbeat failed to connect to standby 'stby_crmsdb'. Error is 16058. PING[ARC1]: Heartbeat failed to connect to standby 'stby_crmsdb'. Error is 16058. PING[ARC1]: Heartbeat failed to connect to standby 'stby_crmsdb'. Error is 16058. PING[ARC1]: Heartbeat failed to connect to standby 'stby_crmsdb'. Error is 16058. PING[ARC1]: Heartbeat failed to connect to standby 'stby_crmsdb'. Error is 16058. PING[ARC1]: Heartbeat failed to connect to standby 'stby_crmsdb'. Error is 16058. PING[ARC1]: Heartbeat failed to connect to standby 'stby_crmsdb'. Error is 16058. WARN: ARC0: Terminating ARCH (pid 32415) hung on a network operation WARN: ARC3: Terminating ARCH (pid 32415) hung on a network operation WARN: ARC2: Terminating ARCH (pid 32415) hung on a network operation ARC2: Error 16198 due to hung ARCH operation to 'stby_crmsdb' PING[ARC2]: Heartbeat failed to connect to standby 'stby_crmsdb'. Error is 12543. PING[ARC2]: Heartbeat failed to connect to standby 'stby_crmsdb'. Error is 12543. PING[ARC2]: Heartbeat failed to connect to standby 'stby_crmsdb'. Error is 12543. PING[ARC2]: Heartbeat failed to connect to standby 'stby_crmsdb'. Error is 12543. PING[ARC2]: Heartbeat failed to connect to standby 'stby_crmsdb'. Error is 12543. PING[ARC2]: Heartbeat failed to connect to standby 'stby_crmsdb'. Error is 12543. NSA: Error 3135 archiving log 1 to 'stby_crmsdb' PING[ARC2]: Heartbeat failed to connect to standby 'stby_crmsdb'. Error is 12543. PING[ARC2]: Heartbeat failed to connect to standby 'stby_crmsdb'. Error is 12543. PING[ARC2]: Heartbeat failed to connect to standby 'stby_crmsdb'. Error is 12543. PING[ARC2]: Heartbeat failed to connect to standby 'stby_crmsdb'. Error is 12543. PING[ARC2]: Heartbeat failed to connect to standby 'stby_crmsdb'. Error is 12543. PING[ARC2]: Heartbeat failed to connect to standby 'stby_crmsdb'. Error is 12543. PING[ARC2]: Heartbeat failed to connect to standby 'stby_crmsdb'. Error is 12543. PING[ARC2]: Heartbeat failed to connect to standby 'stby_crmsdb'. Error is 12543. PING[ARC2]: Heartbeat failed to connect to standby 'stby_crmsdb'. Error is 12543. PING[ARC2]: Heartbeat failed to connect to standby 'stby_crmsdb'. Error is 12543. PING[ARC2]: Heartbeat failed to connect to standby 'stby_crmsdb'. Error is 12543. PING[ARC2]: Heartbeat failed to connect to standby 'stby_crmsdb'. Error is 12543. PING[ARC2]: Heartbeat failed to connect to standby 'stby_crmsdb'. Error is 12543. PING[ARC2]: Heartbeat failed to connect to standby 'stby_crmsdb'. Error is 12537. PING[ARC2]: Heartbeat failed to connect to standby 'stby_crmsdb'. Error is 1034. PING[ARC2]: Heartbeat failed to connect to standby 'stby_crmsdb'. Error is 16058. PING[ARC2]: Heartbeat failed to connect to standby 'stby_crmsdb'. Error is 16058. Error 16058 for archive log file 2 to 'stby_crmsdb' PING[ARC2]: Heartbeat failed to connect to standby 'stby_crmsdb'. Error is 16058. PING[ARC2]: Heartbeat failed to connect to standby 'stby_crmsdb'. Error is 16058. PING[ARC2]: Heartbeat failed to connect to standby 'stby_crmsdb'. Error is 16058. PING[ARC2]: Heartbeat failed to connect to standby 'stby_crmsdb'. Error is 16058. PING[ARC2]: Heartbeat failed to connect to standby 'stby_crmsdb'. Error is 16058. PING[ARC2]: Heartbeat failed to connect to standby 'stby_crmsdb'. Error is 16058. WARN: ARC1: Terminating ARCH (pid 32417) hung on a network operation WARN: ARC0: Terminating ARCH (pid 32417) hung on a network operation ARC0: Error 16198 due to hung ARCH operation to 'stby_crmsdb' WARN: ARC0: Terminating ARCH (pid 32419) hung on a network operation WARN: ARC2: Terminating ARCH (pid 32419) hung on a network operation ARC2: Error 16198 due to hung ARCH operation to 'stby_crmsdb' NSA: Error 3135 archiving log 2 to 'stby_crmsdb' WARN: ARC3: Terminating ARCH (pid 1174) hung on a network operation WARN: ARC2: Terminating ARCH (pid 1174) hung on a network operation ARC2: Error 16198 due to hung ARCH operation to 'stby_crmsdb' PING[ARC2]: Heartbeat failed to connect to standby 'stby_crmsdb'. Error is 12543. PING[ARC2]: Heartbeat failed to connect to standby 'stby_crmsdb'. Error is 12543. PING[ARC2]: Heartbeat failed to connect to standby 'stby_crmsdb'. Error is 12543. PING[ARC2]: Heartbeat failed to connect to standby 'stby_crmsdb'. Error is 12543. PING[ARC2]: Heartbeat failed to connect to standby 'stby_crmsdb'. Error is 12543. 62 rows selected. SYS>select thread#, max(sequence#) from v$archived_log group by thread#; THREAD# MAX(SEQUENCE#) ---------- -------------- 1 14459 ################## on standby ########################## SYS>select thread#, max(sequence#) from v$archived_log where applied='YES' group by thread#; THREAD# MAX(SEQUENCE#) ---------- -------------- 1 14459 SYS>SELECT client_process, process, thread#, sequence#, status FROM v$managed_standby WHERE client_process='LGWR' or process='MRP0' ORDER BY PROCESS; CLIENT_P PROCESS THREAD# SEQUENCE# STATUS -------- --------- ---------- ---------- ------------ N/A MRP0 1 14460 WAIT_FOR_LOG LGWR RFS 1 14460 IDLE thanks
Hello; Generally a Error is 12543 is a firewall or network down on one of the servers. Linux check service iptables status if up... service iptables stop That's the local firewall, if your network has a different firewall contact the network people Closest Oracle note Local Connections Using TCP Fail With TNS-12543 or TNS-12535 to 11.2.0.4 Database (Doc ID 2017460.1) Best Regards mseberg
>> On standby$ service network statusConfigured devices:lo eth0Currently active devices:lo eth0 >> On primaryservice network statusConfigured devices:lo eth0Currently active devices:lo eth0 i have n/w connectivity between two servers.I am sure archives are shipped and also applied If the firewall is down , what can i do ?
Hello; Make sure you did this too. service iptables status try from SQL connecting as sys connect sys/oracle#standby as sysdba connect sys/oracle#primary as sysdba So from the primary connect to standby, and from the standby connect to the primary Best Regards mseberg
ORA-16058 - generally this is a listener error on the standby database. Compare you setup to this Example ( if you make changes restart the listener ) Listener on Primary # listener.ora Network Configuration File: /u01/app/oracle/product/11.2.0/network/admin/listener.ora# Generated by Oracle configuration tools. LISTENER = (DESCRIPTION_LIST = (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = yourdomain.com)(PORT = 1521)) ) ) SID_LIST_LISTENER = (SID_LIST=(SID_DESC=(SID_NAME = PRIMARY) (ORACLE_HOME=/u01/app/oracle/product/11.2.0) (GLOBAL_DBNAME = PRIMARY_DGMGRL.yourdomain.com))) ADR_BASE_LISTENER = /u01/app/oracle INBOUND_CONNECT_TIMEOUT_LISTENER=120 Listener on Standby # listener.ora Network Configuration File: /u01/app/oracle/product/11.2.0/network/admin/listener.ora# Generated by Oracle configuration tools. LISTENER = (DESCRIPTION_LIST = (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = yourdomain.com)(PORT = 1521)) ) ) SID_LIST_LISTENER = (SID_LIST =(SID_DESC =(SID_NAME = STANDBY) (ORACLE_HOME = /u01/app/oracle/product/11.2.0) (SDU=32767) (GLOBAL_DBNAME = STANDBY_DGMGRL.yourdomain.com))) ADR_BASE_LISTENER = /u01/app/oracle INBOUND_CONNECT_TIMEOUT_LISTENER=120 Best Regards mseberg
How frequent are those connection errors? Maybe they are just temporary network errors. Since those connection errors don't have timestamps it is hard to tell. But if that's all of them and you've been running for several weeks for example, then that's a tiny percentage and I wouldn't worry about it.
>> Now i have different error on primart. SYS>select message from v$dataguard_status where dest_id = 2; MESSAGE--------------------------------------------------------------------------------PING[ARC2]: Heartbeat failed to connect to standby 'stby_crmsdb'. Error is 12541.FAL[server, ARC3]: Error 12541 creating remote archivelog file 'stby_crmsdb'
ORA-12541 Is the listener running? Best Regards mseberg
Yes, listener is running.just stopped and restarted. that's it. i can connect from the primary to standby, and from the standby to the primary
Makes me wonder about handat comment about "temporary network errors" If you can connect both ways than the setup is good and you don't have a firewall issue. It really does seem like the network is making Oracle bark Best Regards mseberg
>> on primary now, i do not have any error SYS>select message from v$dataguard_status where dest_id = 2;no rows selected I really wonder. 1) standby database restarted - startup mount 2) Swap file "listener.ora.swp" already exists! . i removed it3) listener has stopped and restarted. that's it.Now error cleared.
Odd stuff. I guess all you can do is keep an eye on it. Best Regards mseberg
I am leaving now. thanks mseberg. I will check it after 10 hours
Odd stuff. I guess all you can do is keep an eye on it. i dont understand any logic. Why the error came ?why it has gone ?what was the actual error ?then how can i keep an eye ? - Just fun. ok. i am leaving now.
I really wonder. 1) standby database restarted - startup mount 2) Swap file "listener.ora.swp" already exists! . i removed it 3) listener has stopped and restarted. that's it. Now error cleared. Sometimes, even though the standby is up and running with MRP active, the primary hesitates to ship the redo to the standby and shouts the error messages related to network (Heartbeat failed or Hung Network) as a network glitch might be on a hung state. In such situations, you can try either of these: 1. Defer the log shipment on primary to the standby and ENABLE it back.2. Cancel the MRP on the standby and restart the recovery.3. If nothing works, try bouncing the standby. HTH -- Shivananda Rao