Mani's Blog

October 24, 2012

ORA-32021: parameter value longer than 255 characters

Filed under: Oracle — mani @ 7:29 pm

I was trying to set service_names, which was really long due to more number of services we needed.   Used ‘,’ as concatenation between multiple values, then worked.

SQL> @enable_services
ALTER SYSTEM SET SERVICE_NAMES=’xno_db_proc.xno.ningops.net, xno_db_membership.xno.ningops.net, xno_db_core_search.xno.ningops.net, xno_db_core_cache.xno.ningops.net,    xno_db_opensocial.xno.ningops.net, xno_db_core_batch.xno.ningops.net, xno_db_core_audit.xno.ningops.net, xno_db_core.xno.ningops.net, xno_db_admin.xno.ningops.net,  xno_core.xno.ningops.net, XNODBCOR’
*
ERROR at line 1:
ORA-32021: parameter value longer than 255 characters

Fix:  Used ‘,’ as concatenation between multiple values, then worked.

[oracle@xnodb911 ~]$ cat enable_services.sql
ALTER SYSTEM SET SERVICE_NAMES=’xno_db_proc.xno.ningops.net, xno_db_membership.xno.ningops.net, xno_db_core_search.xno.ningops.net, xno_db_core_cache.xno.ningops.net,‘,’ xno_db_opensocial.xno.ningops.net, xno_db_core_batch.xno.ningops.net, xno_db_core_audit.xno.ningops.net, xno_db_core.xno.ningops.net, xno_db_admin.xno.ningops.net,‘,’xno_core.xno.ningops.net, XNODBCOR’;

SQL> @enable_services.sql

System altered.

SQL> show parameter service_names

NAME                     TYPE
———————————— ——————————–
VALUE
——————————
service_names                 string
xno_db_proc.xno.ningops.net, x
no_db_membership.xno.ningops.n
et, xno_db_core_search.xno.nin
gops.net, xno_db_core_cache.xn
o.ningops.net,,  xno_db_openso
cial.xno.ningops.net, xno_db_c
ore_batch.xno.ningops.net, xno
_db_core_audit.xno.ningops.net

NAME                     TYPE
———————————— ——————————–
VALUE
——————————
, xno_db_core.xno.ningops.net,
xno_db_admin.xno.ningops.net,
, xno_core.xno.ningops.net, XN
ODBCOR
SQL>

October 10, 2012

Oracle ASM disk creation failed. Marking disk “%s” as an ASM disk: [FAILED]

Filed under: ASM,Database,Oracle — mani @ 10:21 pm

We have a RAC database, we are converting to Non-RAC (Stand-alone) DB, and also need to migrate data off SAN storage.  I ran into this error while I am creating ASM disk ( after adding 2 new local disks).

Here is the error I ran into.

# /etc/init.d/oracleasm createdisk asm_ssd1 /dev/sdz1
Marking disk “asm_ssd1” as an ASM disk:                    [FAILED]

As soon the disk has been added to system, is configured via multipath and created device under /dev/mapper.  As I don’t want to use via multipath device, so what I did was.

1. Grabbed device id by ls -lrt /dev/disk/by-id

2. Added this device id in backlist block of /etc/multipath.conf file

devnode_blacklist {
wwid 3600508e000000000d02538430ed9c60b
wwid 35000c5003192cd97
wwid 35000c500333728e3
devnode “^(ram|raw|loop|fd|md|dm-|sr|scd|st)[0-9]*”
devnode “^hd[a-z]”
devnode “^cciss!c[0-9]d[0-9]*”
}

3. run /etc/init.d/multipathd restart

Now I am able to create ASM disk properly.

# /etc/init.d/oracleasm createdisk asm_ssd1 /dev/sdz1
Marking disk “asm_ssd1” as an ASM disk:                    [  OK  ]
# /etc/init.d/oracleasm createdisk asm_ssd2 /dev/sdaa1
Marking disk “asm_ssd2” as an ASM disk:                    [  OK  ]

Now I can see newly added disks.
# /etc/init.d/oracleasm listdisks
ASM_DATA01
ASM_DATA02
ASM_REDO01
ASM_SSD1
ASM_SSD2

October 8, 2012

ORA-16789: standby redo logs not configured

Filed under: Data Guard Broker,Database,Dataguard,Oracle — mani @ 9:42 pm
Tags: ,

In our environment, Dataguard Manager log was showing following errors.

DG 2012-10-08-21:23:11        0 2 0 RSM0: HEALTH CHECK WARNING: ORA-16789: standby redo logs not configured
DG 2012-10-08-21:23:11        0 2 760559130 Operation CTL_GET_STATUS continuing with warning, status = ORA-16789
DG 2012-10-08-21:23:11        0 2 760559130 Operation CTL_GET_STATUS continuing with warning, status = ORA-16809
DG 2012-10-08-21:24:11        0 2 0 RSM Error: LogXptMode value ‘ASYNC’ of requires this database to have status redo logs, but they are not configured.

Show Configuration reports warning “ORA-16608: one or more databases have warnings”

DGMGRL> show configuration

Configuration
Name:                aclu1c
Enabled:             YES
Protection Mode:     MaxPerformance
Databases:
xnodb01c   – Primary database
xnodb01cdg – Physical standby database

Fast-Start Failover: DISABLED

Current status for “aclu1c”:
Warning: ORA-16608: one or more databases have warnings

show database verbose xnodb01cdg  returned success.

show database verbose xnodb01c returned errors, so I am sure the primary DB has issue.
Solution: is to add standby log files to primary DB.

SQL> ALTER DATABASE ADD STANDBY LOGFILE GROUP 31 ( ‘+XN_DATA’) SIZE 209715200 reuse;

Database altered.

SQL> ALTER DATABASE ADD STANDBY LOGFILE GROUP 32 ( ‘+XN_DATA’) SIZE 209715200 reuse;

Database altered.

SQL> ALTER DATABASE ADD STANDBY LOGFILE GROUP 33 ( ‘+XN_DATA’) SIZE 209715200 reuse;

Database altered.

SQL> ALTER DATABASE ADD STANDBY LOGFILE GROUP 34 ( ‘+XN_DATA’) SIZE 209715200 reuse;

Database altered.

SQL> ALTER DATABASE ADD STANDBY LOGFILE GROUP 35 ( ‘+XN_DATA’) SIZE 209715200 reuse;

Database altered.

Problem solved:

After adding all above standby log files,   Dataguard log stopped reporting the error.  Also dgmgrl stopped reporting the warnings.

DGMGRL> show configuration

Configuration
Name:                aclu1c
Enabled:             YES
Protection Mode:     MaxPerformance
Databases:
xnodb01c   – Primary database
xnodb01cdg – Physical standby database

Fast-Start Failover: DISABLED

Current status for “aclu1c”:
SUCCESS

DGMGRL>

 

Create a free website or blog at WordPress.com.