reffec.com

Investigating Oracle errors in Software Build barcode code39 in Software Investigating Oracle errors

Investigating Oracle errors generate, create code-39 none in software projects Visual Basic Should an Oracle error ca Code-39 for None use the Manager, Extract, and Replicat process to abend, their corresponding report files will contain the Oracle error number and message. The following example shows an ORA-03113 error from a failed Replicat process:. 2010-11-21 11:10:38 GGS E RROR 182 OCI Error executing single row select (status = 3113-ORA-03113: end-of-file on communication channel. This is useful in determi Software 39 barcode ning the root cause, but maybe it doesn"t provide enough detail on how to progress the issue. Luckily help is at hand; every Oracle home contains an error lookup utility, which nine times out of ten provides additional information about the error and instruction in how to fix it. The utility is oerr, located in the $ORACLE_HOME/bin directory on Linux versions.

. oerr accepts two argument s, the error group name and the error number. So let"s execute oerr on the Linux command line and see what is says about ORA-03113..

[oracle@dbserver1 dirrpt] Software USS Code 39 $ oerr ora 3113 03113, 00000, "end-of-file on communication channel" // *Cause: The connection between Client and Server process was broken. [ 218 ]. 10 // *Action: There was a communication error that requires further investigation. // setup. // test to // file // First, check for network problems and review the SQL*Net Also, look in the alert.

log file for any errors. Finally, see whether the server process is dead and whether a trace was generated at failure time..

Perfect, that is just the Code 3/9 for None right approach we should adopt to resolve the communication problem in our GoldenGate environment.. Exception handling GoldenGate does not provi Software 3 of 9 barcode de a standard exceptions handler. By default, a Replicat process will abend should any operational failure occur, and will rollback the transaction to the last known checkpoint. This may not be ideal in a production environment.

The HANDLECOLLISIONS and NOHANDLECOLLISIONS parameters can be used to control whether or not a Replicat process tries to resolve duplicate record and missing record errors, but should these errors be ignored The way to determine what error has occurred, by which Replicat, caused by what data, is to create an Exceptions handler.. Creating an Exceptions handler The following steps creat Software Code 39 Full ASCII e an Exceptions handler that will trap and log the specified Oracle error(s), but allow the Replicat to continue to process data: 1. The first step is to create an Exceptions table, as shown in the example DDL:. create table ggs_admin.ex ceptions ( rep_name varchar2(8) , table_name varchar2(61) , errno number , dberrmsg varchar2(4000) , optype varchar2(20) , errtype varchar2(20) , logrba number , logposition number , committimestamp timestamp [ 219 ]. Troubleshooting GoldenGat Software Code 39 Full ASCII e ); ALTER TABLE ggs_admin.exceptions ADD ( CONSTRAINT PK_CTS PRIMARY KEY (logrba, logposition, committimestamp) USING INDEX PCTFREE 0 TABLESPACE MY_INDEXES);. The Exceptions table must be created in the GoldenGate Admin user schema. It can log exception data for all Replicat processes. 2.

Edit each Replicat process parameter file and add the exception handler Macro code block.. [oracle@dbserver2 ggs]$ g barcode 3/9 for None gsci GGSCI (dbserver2) 1> edit params RTARGET1 -- Start of the macro MACRO #exception_handler BEGIN , TARGET ggs_admin.exceptions , COLMAP ( rep_name = "RTARGET1" , table_name = @GETENV ("GGHEADER", "TABLENAME") , errno = @GETENV ("LASTERR", "DBERRNUM") , dberrmsg = @GETENV ("LASTERR", "DBERRMSG") , optype = @GETENV ("LASTERR", "OPTYPE") , errtype = @GETENV ("LASTERR", "ERRTYPE") , logrba = @GETENV ("GGHEADER", "LOGRBA") , logposition = @GETENV ("GGHEADER", "LOGPOSITION") , committimestamp = @GETENV ("GGHEADER", "COMMITTIMESTAMP")) , INSERTALLRECORDS , EXCEPTIONSONLY; END; -- End of the macro. 3. Remaining within the e ditor (vi), edit the MAP statements to include the call to the Macro; #exception_handler(). Also, add the REPERROR parameter to reference to the Oracle error(s) you wish to trap.

. REPERROR (DEFAULT, EXCEPT ANSI/AIM Code 39 for None ION) REPERROR (DEFAULT2, ABEND) REPERROR (-1, EXCEPTION) MAP SRC.ORDERS, TARGET TGT.ORDERS; MAP SRC.

ORDERS #exception_handler() MAP SRC.ORDER_ITEMS, TARGET TGT.ORDER_ITEMS; MAP SRC.

ORDER_ITEMS #exception_handler() [ 220 ]. 10 MAP SRC.PRODUCTS, TAR GET TGT.PRODUCTS; MAP SRC.

PRODUCTS #exception_handler(). The REPERROR parameter co Software Code 3/9 ntrols how the Replicat process responds to errors when executing the MAP statement. The DEFAULT option sets a global response to all errors except those for which explicit REPERROR statements are specified. For example, a MAP statement to trap ORAMAP SRC.

ORDERS, TARGET TGT.ORDERS, REPERROR (-1403, EXCEPTION);. 01403: "no data found" er ror would be configured as follows:. The DEFAULT2 option speci barcode code39 for None fies a "catch all" action for any unanticipated Oracle errors that may occur. In the example in step 3, the Replicat process will abend if a unhandled exception occurs. 1.

Now stop and start the Replicat process.. GGSCI (dbserver2) 3> s top REPLICAT RTARGET1 Sending STOP request to REPLICAT RTARGET1 ...

Request processed. GGSCI (dbserver2) 4> start replicat RTARGET1 Sending START request to MANAGER ..

. REPLICAT RTARGET1 starting.
Copyright © reffec.com . All rights reserved.