My Oracle Support Banner

Logical Standby SQL Apply Fails with ORA-06550, PLS-00103 (Doc ID 2752469.1)

Last updated on FEBRUARY 23, 2021

Applies to:

Oracle Database - Enterprise Edition - Version 12.1.0.2 and later
Information in this document applies to any platform.

Symptoms

Logical Standby SQL Apply fails with ORA-06550, PLS-00103.

Alert log on logical standby:

Tue Oct 20 20:09:47 2020
LOGSTDBY: SQL Apply about to stop with ORA-604
LOGSTDBY: SQL Apply finished logging error information
LOGSTDBY: SQL Apply about to stop with ORA-6550
LOGSTDBY: SQL Apply finished logging error information
Tue Oct 20 20:09:47 2020
LOGSTDBY Apply process AS02 server id=2 pid=64 OS id=17807 stopped
Tue Oct 20 20:09:47 2020
Errors in file <PATH>/<SID>_as02_17807.trc:
ORA-06550: line 1, column 158
PLS-00103: Encountered the symbol "end-of-file" when expecting one of the following:

   ( - + case mod new not null <an identifier>
   <a double-quoted delimited-identifier> <a bind variable>
   continue avg count current exists max min prior sql stddev
   sum variance execute forall merge time timestamp interval
   date <a string literal with character set specification>
   <a number> <a single-quoted SQL string> pipe
   <an alternatively-quoted string literal with character set specification>

Apply Server's (ASxx) trace file indicates that operation against SYSTEM.LOGSTDBY$PARAMETERS fails like below.

LOGSTDBY: SQL Apply about to stop with ORA-604
Logging additional information for triaging:

COLUMN INFO:
data for obj#=13862, thr: 1, rba: 0x0097.00000008.10, new 7, old 0
(NEW): element[0], segcol# 1, size 184, data =  62 65 67 69 6e 20 73 79 73 2e 64 62 6d 73 5f 69 6e 74 65 72 6e 61 6c 5f 6c 6f 67 73 74 64 62
79 2e 70 61 72 69 6e 73 28 4e 41 4d 45 5f 4e 3d 3e 27 4c 41 53 54 5f 4c 4f 47 53 54 44 42 59 5f 42 55 49 4c 44 27 2c
 56 41 4c 55 45 5f 4e 3d 3e 27 36 30 33 39 38 35 38 37 36 27 2c 54 59 50 45 5f 4e 3d 3e 33 2c 53 43 4e 5f 4e 3d 3e 4e 55 4c 4c 2c 53 50 41 52
 45 31 5f 4e 3d 3e 4e 55 4c 4c 2c 53 50 41 52 45 32 5f 4e 3d 3e 4e 55 4c 4c 2c 53 50 41 52 45 33 5f 4e 3d 3e 4e 55 4c
 4c 2c 0 5f 4e 3d 3e 4e 55 4c 4c 2c 0 5f 4e 3d 3e 4e 55 4c 4c 29 3b 20 65 6e 64 3b
(NEW): element[1], segcol# 2, size 9, data =  36 30 33 39 38 35 38 37 36
(NEW): element[2], segcol# 3, size 2, data =  c1 4
(NEW): element[3], segcol# 4, size 0, data =
(NEW): element[4], segcol# 5, size 0, data =
(NEW): element[5], segcol# 6, size 0, data =
(NEW): element[6], segcol# 7, size 0, data =

KEY VALUES:
COLUMN INFO FOR KEYID 0:
data for obj#=13862, thr: 1, rba: 0x0097.00000008.10, new 0, old 0

ERROR INFORMATION:
PRIMARY TXN  xid: 0x0003.01f.0000f905 (XIDUSN = 3, XIDSLT = 31, XIDSQN = 63749)
start scn: 0x0000.240017d8 (603985880) commit scn: 0x0000.240017d9 (603985881)
LOCAL XID: 30.15.35896 Start SCN: 604028841 Current SCN: 604028842

LOCAL DICTIONARY:
TABLE: SYSTEM.LOGSTDBY$PARAMETERS
TABLE INFO:
-----------

LOG  COMPRSS     CMPRSS_FOR   TABLESPACE      ROW_MOVE CLUSTER_NAME
--------------------------------------------------------------------------------
YES  DISABLE     NULL         SYSTEM          DISABLED

COLUMN INFO:
-----------

NAME                            TYPE                  COL#  SCOL# ICOL# HDN VIR
--------------------------------------------------------------------------------
NAME                            VARCHAR2              1     1     1     NO  NO
VALUE                           VARCHAR2              2     2     2     NO  NO
TYPE                            NUMBER                3     3     3     NO  NO
SCN                             NUMBER                4     4     4     NO  NO
SPARE1                          NUMBER                5     5     5     NO  NO
SPARE2                          NUMBER                6     6     6     NO  NO
SPARE3                          VARCHAR2              7     7     7     NO  NO
SYS_STS90I0TV5BWQ1A16YH4SC_BL2  NUMBER                0     0     8     YES YES
SYS_STSB5FK0OWTNZI5FJ1Q6X77MDB  NUMBER                0     0     9     YES YES

Changes

 Create a new logical standby and start SQL Apply.

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.