Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Re: coredumps when running sqlplus

Re: coredumps when running sqlplus

From: Sybrand Bakker <postbus_at_sybrandb.demon.nl>
Date: Tue, 27 Apr 1999 20:17:42 +0200
Message-ID: <925236927.11399.0.rover.d4ee154e@news.demon.nl>


Definitely looks like sqlnet.
You seem to have defined an interchange between two protocol, and the interchange can't be started. This can well be caused by two different community names in tnsnames.ora, where you only need one. Without your sqlnet.ora, listener.ora and tnsnames.ora at hand, it is difficult to resolve it.

Hth,

Sybrand Bakker, Oracle DBA

bliss wrote in message <7g4jas$1v29$1_at_beast.euro.net>...
>when i run sqlplus on our hpux 10.20 system, oracle 7.3.4, sometimes
sqlplus
>coredumps (memoryfault)
>can anyone tell me how to solve this please?
>below is the top part of the coredump
>i apologize for the lenght of this message
>
><HP-UX
>prisal2
>B.10.20
>9000/810
>2013412181
>sqlplus
>cnno
>CLEAR COLUMNS
>TTITLE OFF
>SET VERIFY ON
>SET FEED ON
>SETUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUU
U
>UUUUUUU?
>cnno
>\B$Revision: 92453-07 linker linker crt0.o B.10.12 960617 $
>/usr/lib/dld.sl
>ERROR: mmap failed for dld
>SQL>
>OPS$PRISALPR
>/db/prisalpr/129/uitvoer/lijsten/05/LIJST689.lst
>spool
>/db/prisalpr/sql/M025A689.sql
>/users/oracle/app/oracle/product/7.3.4/sqlplus/admin/glogin.sql
> cpycon.pc
> cpydis.pc
>Production
> cpytbl.pc
>HP-UX
>prisal2
>B.10.20
>9000/810
>2013412181
>nscontrol
>nricall
>entry
>Route global or NPD global not properly initialized
>exit
>nricdpii is %d and new nricdpis is %d
>%d%d
>Poorly formed NS address %s
>exit
>Unable to allocate local connection descriptor buffer
>local
>Unable to allocate routing connection descriptor buffer
>routing
>Unable to allocate local outgoing connection descriptor buffer
>local outgoing
>DESCRIPTION
>(DESCRIPTION=)
>DESCRIPTION/FADRL
>Need failed address information
>FADRL/COMMUNITY_LIST
>could not copy failed address binding
>DESCRIPTION/FADRL
>Failed to copy connect binding for routing
>DESCRIPTION/ADDRESS
>DESCRIPTION/ADDRESS_LIST
>DESCRIPTION/ADDRESS_LIST
>Got routable address information
>DESCRIPTION/ADDRESS/PROTOCOL
>Removed IPC address from address list
>Making call with following address information: %s
>Not enough memory to copy returned data into. Closing down connection
>(FADRL=(FC=)(FG=))
>Failed to copy originating community name value binding
>(ADDRESS_LIST=)
>Unable to create empty addlist for possible addresses
>Exiting NRICALL with following termination result %d
>exit
>nricdt
>entry
>Calling with outgoing connect data %s
>Async nscall partially completed: returned data %s
>Call successful: returned data %s
>exit
>Call failed...
>exit
>Call made to destination
>exit
>DESCRIPTION/ADDRESS
>exit
>Processing address list so continuing
>exit
>Call failed because intermediate interchange failed...
>exit
>Got refuse from call
>refused data: %s
>exit
>Application refuse %s
>exit
>exit
>nricpgi
>entry
>DESCRIPTION/GWAY/ERROR
>exit
>DESCRIPTION/GWAY/CMANAGER_NAME
>NOROUTE
>REDFAIL
>NOCONN
>NETWORK
>ACPTFAIL
>SHUTDOWN
>This is a P2 bug. The interchange is returning data in wrong format.
>exit
>DESCRIPTION/GWAY/ERROR_STACK
>Remote result descriptor: %u,%u,%u,%u
>%u%u%u%u
>DESCRIPTION/GWAY/FADRL
>Reroute around possibly failed interchange
>exit
>exit
>Failure of call through interchange pump
>DESCRIPTION/ADDRESS
>exit
>exit
>Network error failure of call through interchange pump
>DESCRIPTION/ADDRESS
>exit
>exit
>DESCRIPTION/GWAY/RED
>Got redirect from interchange
>NONE
>DESCRIPTION/GWAY/DCNME
>exit
>DESCRIPTION/ADDRESS
>exit
>exit
>Redirect failure bad route
>exit
>RED/ADDRESS
>exit
>DESCRIPTION/ADDRESS/CMANAGER_NAME
>ADDRESS/CMANAGER_NAME
>DESCRIPTION/ADDRESS/COMMUNITY
>(FADR=(COMMUNITY=%s)(CMANAGER_NAME=%s))
>FADRL
>FADRL/TMP
>DESCRIPTION/ADDRESS
>exit
>Continuing after redirect
>exit
>exit
>nricfg
>entry
>Get failed interchange information
>DESCRIPTION/ADDRESS
>ADDRESS/CMANAGER_NAME
>ADDRESS/COMMUNITY
>Unable to find interchange name or community in address
>exit
>FADRL/FG
>FADRL/FC
>No failed address CMANAGER or Communitycomponent in failed address list
>exit
>FG/%s
>Failed CMANAGER_NAME=%s component already in failed address list
>exit
>(%s=(T=0)(C=%s))
>exit
>DESCRIPTION/ADDRESS
>exit
>Updated failed interchange information
>exit
>Bad route update entries.. Failing
>exit
>nrifcd
>entry
>exit
>exit
>%s/C
>exit
>exit
>exit
>nricfg
>entry
>exit
>nricie
>entry
>Result descriptor: %u,%u,%u,%u
>%u%u%u%u
>Result descriptor: %u,%u,%u,%u
>Result descriptor: %u,%u,%u,%u from Interchange: %s
>%u%u%u%u
>%u%u%u%u%s
>exit
>nsdo
>NSPTMK
>NSPTMK
>NSPTMK
>NSPTMK
>from
>from
>nsdowt4
>nsdofls
>NSPTDA
>NSPTDA
>nsdoacts
>nsdootini
>nsdootsnd
>NSPTCNL
>NSPTCNL
>dlcr.rdbms.omd
>nnfgiinit
>entry
>NETWORK
>Name server API init failed, no error message file
>NETWORK
>Native name server API init failed, no error message file
>Cannot initialize %s naming adapter.
>Library %s does not exist or is invalid.
>nnfgspd
>entry
>
>
>
>
>
>
>
>
Received on Tue Apr 27 1999 - 13:17:42 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US