Execution Of OCI Application Causes Core Dump And OCI21500 Error (Doc ID 430683.1) In this Document Symptoms Changes Cause Solution References APPLIES TO: Oracle Database Enterprise Edition Version 10.2.0.1 to 10.2.0.2 [Release 10.2] SQL*Plus Version 10.2.0.1 to 10.2.0.2 [Release Oracle10g] Information in this document applies to any platform. ***Checked for relevance on 13May2014*** AIX 5L Based System (64bit) 5.3, and can also occur on most UNIX OS with 64 bit. SYMPTOMS Execution of OCI application causes core dump and throws error OCI21500. OCI‐21500: Message 21500 not found; No message file for product=RDBMS, facility=OCI; arguments: [kope2uattr:charpass] [0x0000000C1] [] [] When the error happens the users were setting "set serveroutput on" from the OCI application session. While the same application works fine for ORACLE user. CHANGES Upgrading from Previous Version of Oracle to the Later Version of Oracle. CAUSE OCI application on Server or Client using Bequeth (BEQ) mode (an empty or NULL connect string in OCIServerAttach call) requires that the TWO_TASK variable should be set. These issues are generic and could happen to any UNIX 64 bit OS and for protocols like TCP and BEQ as well. Bug 4860003 , SQLPLUS CRASHES WITH OCI21500 [KOXSIHREAD1] AND DUMPS CORE SQLPLUS crashes with OCI21500 error and a core dump when "set serveroutput on" is run in the same session where startup command is executed. SOLUTION 1. Set TWO_TASK to a fully qualified connect string, or if TNS_ADMIN is set, then you can set

Document 430683

Download PDF Report

Upload
randall-may
View
9
Download
6

Embed Size (px)

DESCRIPTION

Doc 1

Citation preview

ExecutionOfOCIApplicationCausesCoreDumpAndOCI21500Error(DocID430683.1)

InthisDocument

SymptomsChangesCauseSolutionReferences

APPLIESTO:

OracleDatabaseEnterpriseEditionVersion10.2.0.1to10.2.0.2[Release10.2]SQL*PlusVersion10.2.0.1to10.2.0.2[ReleaseOracle10g]Informationinthisdocumentappliestoanyplatform.***Checkedforrelevanceon13May2014***

AIX5LBasedSystem(64bit)5.3,andcanalsooccuronmostUNIXOSwith64bit.

SYMPTOMS

ExecutionofOCIapplicationcausescoredumpandthrowserrorOCI21500.

OCI21500:Message21500notfound;Nomessagefileforproduct=RDBMS,facility=OCI;arguments:

[kope2uattr:charpass][0x0000000C1][][]

Whentheerrorhappenstheusersweresetting"setserveroutputon"fromtheOCIapplicationsession.WhilethesameapplicationworksfineforORACLEuser.

CHANGES

UpgradingfromPreviousVersionofOracletotheLaterVersionofOracle.

CAUSE

OCIapplicationonServerorClientusingBequeth(BEQ)mode(anemptyorNULLconnectstringinOCIServerAttachcall)requiresthattheTWO_TASKvariableshouldbeset.TheseissuesaregenericandcouldhappentoanyUNIX64bitOSandforprotocolslikeTCPandBEQaswell.

Bug4860003,SQLPLUSCRASHESWITHOCI21500[KOXSIHREAD1]ANDDUMPSCORE

SQLPLUScrasheswithOCI21500errorandacoredumpwhen"setserveroutputon"isruninthesamesessionwherestartupcommandisexecuted.

SOLUTION

1.SetTWO_TASKtoafullyqualifiedconnectstring,orifTNS_ADMINisset,thenyoucanset
ittoatnsnames.oraentry.

e.g.,

TWO_TASK="(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(Host=myhost)(Port=10201)))(CONNECT_DATA=(SID=DB102X)))"

exportTWO_TASK

Pleasenotethatyourhost,port,SIDcouldbedifferentthantheabove.

i.e.,SpecifythefullconnectdescriptorintheTWO_TASKenvironmentvariable,sameasinyourtnsnames.ora

2.Echothe$TWO_TASKvariableandensurethatitissettothecorrectvalue.

e.g.,

echo$TWO_TASK

3.Changethepermissionsof$ORACLE_HOMEdirectory,i.e.,

chmod+R755

toalldirectoriesunderORACLE_HOME.

Ifyoucannotchangethepermissionsontheentire$ORACLE_HOMEdirectory,youwouldatleastneedtochangethepermisssionsforthefollowingdirectories:

chmod755$ORACLE_HOME/nlschmod755$ORACLE_HOME/nls/datachmod755$ORACLE_HOME/nls/mesg

AlternativelyyoucanapplythefollowingpatchbasedonyourOS:

Patch4860003forHPUXPARISC64bitPatch6019127forSUNSolarisSPARC64bit

PleaseNotethat'Bug4860003:SQLPLUSCRASHESWITHOCI21500[KOXSIHREAD1]ANDDUMPSCORE'showsupwhentryingtosetsomeparametersontheSQLPLUSproductbuttherealproblemhappensatthegenericpartofthecode.ThecodelinesareinternaltoRDBMSGeneric.Problemwaswithpicklingandunpicklingofimageson64bit
platforms.ThisproblemthusisnotpotentiallyspecifictoSQL*PlusanditseemsspecifictotheObjectManagementlayer.ForSupportreasons,sinceitisshowsupontheSQLPLUSproduct,itmostlygetsroutedtothisProductset.