Symptom
- db2diag.log . . . myriads of SQL1776N . . .
YYYY-MM-DD-24.mm.ss.msmsms+### I11835E761 LEVEL: Warning
PID : ##### TID : ############# PROC : db2sysc 0
INSTANCE: db2<sid> NODE : 000 DB : <SID>
AUTHID : SAPSCP HOSTNAME: <present standby_hostname>
. . .
FUNCTION: DB2 UDB, High Availability Disaster Recovery, hdrCheckDb, probe:18200
MESSAGE : SQL1776N The command cannot be issued on an HADR database. Reason code = "1".
. . .
Connections are not allowed on a standby database. - R3trans -d . . . trans.log . . .
SQL1776N The command cannot be issued on an HADR database. Reason code = "1. - db2 connect to <SID> . . . command line connection on standby linux server . . .
SQL1776N The command cannot be issued on an HADR database. Reason code = "1.
Read more...
Environment
IBM Db2 LUW
DB2 HADR with Tivoli Clustering software . . . Tivoli System Automation for Mutliplatforms (TSAMP) . . . on top
Product
SAP Supply Chain Management 7.0
Keywords
KBA , BC-DB-DB6 , DB2 Universal Database for Unix / NT , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.