Db2diag.log issue in DB2

Hi All,
We are repetitively getting severe error message in DB2  database. Please advise on this.
2014-08-07-10.45.03.030954+060 I14065240A184      LEVEL: Severe
PID:10944994 TID:74889 NODE:000 Title: **** DRDA CMNMGR CB ****
Dump File: /db2/fmp/db2dump/10944994.74889.000.dump.bin
2014-08-07-10.45.03.032407+060 I14065425A181      LEVEL: Severe
PID:10944994 TID:74889 NODE:000 Title: **** DSS SEGMENT ****
Dump File: /db2/fmp/db2dump/10944994.74889.000.dump.bin
2014-08-07-10.45.03.033169+060 I14065607A184      LEVEL: Severe
PID:10944994 TID:74889 NODE:000 Title: **** RECEIVE BUFFER ****
Dump File: /db2/fmp/db2dump/10944994.74889.000.dump.bin
2014-08-07-10.45.03.033957+060 I14065792A238      LEVEL: Severe
PID:10944994 TID:74889 NODE:000 Title: **** SEND BUFFERS ****
Dump File: /db2/fmp/db2dump/10944994.74889.000.dump.bin
Dump with error: Error 65706 occurred. ( rc = 0x100aa )
1833 Aug 07 07:04 db2locktimeout.0.3856.2014-08-07-07-04-58
-rw-r--r--    1 db2fmp   dbfmpadm     250773 Aug 07 07:05 10944994.221612.000.dump.bin
-rw-r--r--    1 db2fmp   dbfmpadm    1733457 Aug 07 07:05 10944994.279501.000.dump.bin
-rw-r--r--    1 db2fmp   dbfmpadm     512284 Aug 07 07:10 10944994.189348.000.dump.bin
-rw-r--r--    1 db2fmp   dbfmpadm    1666934 Aug 07 07:15 10944994.251255.000.dump.bin
-rw-r--r--    1 db2fmp   dbfmpadm    1456576 Aug 07 07:15 10944994.220776.000.dump.bin
-rw-r--r--    1 db2fmp   dbfmpadm     716526 Aug 07 07:15 10944994.186209.000.dump.bin
-rw-r--r--    1 db2fmp   dbfmpadm     226391 Aug 07 07:20 10944994.202921.000.dump.bin
-rw-r-----    1 db2fmp   dbfmpadm       1833 Aug 07 07:20 db2locktimeout.0.3856.2014-08-07-07-20-03
-rw-r--r--    1 db2fmp   dbfmpadm     427893 Aug 07 07:20 10944994.258979.000.dump.bin
-rw-r--r--    1 db2fmp   dbfmpadm    1250050 Aug 07 07:30 10944994.234475.000.dump.bin
-rw-r--r--    1 db2fmp   dbfmpadm    1188238 Aug 07 07:30 10944994.90388.000.dump.bin
-rw-r--r--    1 db2fmp   dbfmpadm    1274291 Aug 07 07:35 10944994.259795.000.dump.bin
Regards,
Raja

Hi,
Also getting below error message.
2014-08-07-10.55.01.768463+060 I14131030A1270     LEVEL: Severe
PID     : 10944994             TID  : 186209      PROC : db2sysc 0
INSTANCE: db2fcp               NODE : 000
APPHDL  : 0-51945
EDUID   : 186209               EDUNAME: db2agent (idle) 0
FUNCTION: DB2 UDB, DRDA Communication Manager, sqljcReceive, probe:30
MESSAGE : ZRC=0x81360010=-2127167472=SQLZ_RC_CMPARM, SQLT_SQLJC
          "CM parameter bad"
DATA #1 : String, 11 bytes
CCI Error:
DATA #2 : unsigned integer, 8 bytes
68
CALLSTCK: (Static functions may not be resolved correctly, as they are resolved to the nearest symbol)
  [0] 0x090000000D21AFB0 pdLog + 0xE0
  [1] 0x090000000B9AA2DC sqljcLogCCIError__FP10sqljCmnMgrPCcP12SQLCC_COND_TUclN35 + 0x234
  [2] 0x090000000B9AB5AC sqljcLogCCIError__FP10sqljCmnMgrPCcP12SQLCC_COND_TUclN35@glueDAC + 0x78
  [3] 0x090000000A594B84 sqljcReceive__FP10sqljCmnMgr + 0x278
  [4] 0x090000000D2D859C @63@sqljsRecv__FP8sqeAgentP13sqljsDrdaAsCb + 0x100
  [5] 0x090000000D2D8370 @63@sqljsDrdaAsInnerDriver__FP18SQLCC_INITSTRUCT_Tb + 0x254
  [6] 0x090000000D2D7E60 sqljsDrdaAsDriver__FP18SQLCC_INITSTRUCT_T + 0xEC
  [7] 0x090000000D2540B0 RunEDU__8sqeAgentFv + 0x2F4
  [8] 0x090000000D2502EC EDUDriver__9sqzEDUObjFv + 0xE4
  [9] 0x090000000D25C4B0 sqloEDUEntry + 0x260
Rgards,
Raj

Similar Messages

  • Error Database DB2 (db2diag.log)

    Hi, I nedd help.
    The log db2diag.log show message error, and database colapse every 48 hours.
    2011-08-01-08.59.46.316326-300 I30710990A559      LEVEL: Warning
    PID     : 14564                TID  : 427         PROC : db2sysc 0
    INSTANCE: db2epd               NODE : 000         DB   : EPD
    APPHDL  : 0-94                 APPID: 10.20.0.61.53713.110801135412
    AUTHID  : SAPEPDDB
    EDUID   : 427                  EDUNAME: db2agent (EPD) 0
    FUNCTION: DB2 UDB, data protection services, sqlpgWaitForLrecBufferLimit, probe:410
    MESSAGE : ZRC=0x870F0151=-2029059759=SQLO_WP_TERM
              "The waitpost area has been terminated"
    DATA #1 : String, 10 bytes
    Ignore rc.
    please help.

    Hi I would like to have more informations. In db2diag, do you  have any LEVEL : Error or Severe messages ?.  The log you put is a warning
    thanks

  • Fast growing db2diag.log (FP4 V9.5)

    Does anyone have experiences with V9.5 FP4SAP?
    We have implemented this FP4 last week (from FP2a). Since this a db2diag.log of about 1MB were written (and the system usage is really low).
    We have another system on FP2a which is used heavier (as a productive system) and the db2diag.log is about 2,5 MB within two months.
    We have checked SAP note 1086130 for DB parameters and did not find a required change (from FP2a to FP4).
    Any idea is welcome!
    Best regards.

    db2diag.log extract 2009-08-02 23:00-23:59
    2009-08-02-23.24.20.577179+120 I1019336A362       LEVEL: Warning
    PID     : 602270               TID  : 4114        PROC : db2sysc 0
    INSTANCE: db2mes               NODE : 000
    EDUID   : 4114                 EDUNAME: db2logmgr (MES) 0
    FUNCTION: DB2 UDB, data protection services, sqlpgArchiveLogFile, probe:3108
    MESSAGE : Started archive for log file S0001678.LOG.
    2009-08-02-23.24.21.914535+120 I1019699A422       LEVEL: Warning
    PID     : 602270               TID  : 4114        PROC : db2sysc 0
    INSTANCE: db2mes               NODE : 000
    EDUID   : 4114                 EDUNAME: db2logmgr (MES) 0
    FUNCTION: DB2 UDB, data protection services, sqlpgArchiveLogFile, probe:3180
    MESSAGE : Completed archive for log file S0001678.LOG to TSM chain 0 from
              /db2/MES/log_dir/NODE0000/.
    2009-08-02-23.28.53.621596+120 I1020122A483       LEVEL: Event
    PID     : 602270               TID  : 3342        PROC : db2sysc 0
    INSTANCE: db2mes               NODE : 000         DB   : MES
    APPHDL  : 0-8                  APPID: *LOCAL.DB2.090729131318
    AUTHID  : MESADM 
    EDUID   : 3342                 EDUNAME: db2stmm (MES) 0
    FUNCTION: DB2 UDB, config/install, sqlfLogUpdateCfgParam, probe:20
    CHANGE  : STMM CFG DB MES: "Locklist" From: "3712" <automatic>  To: "3552" <automatic>
    2009-08-02-23.28.53.627724+120 I1020606A545       LEVEL: Event
    PID     : 602270               TID  : 3342        PROC : db2sysc 0
    INSTANCE: db2mes               NODE : 000         DB   : MES
    APPHDL  : 0-8                  APPID: *LOCAL.DB2.090729131318
    AUTHID  : MESADM 
    EDUID   : 3342                 EDUNAME: db2stmm (MES) 0
    FUNCTION: DB2 UDB, access plan manager, sqlra_resize_pckcache, probe:150
    CHANGE  : APM : Package Cache : FROM "5208760" : TO "4191641" : success
    IMPACT  : None
    DATA #1 : String, 29 bytes
    Package Cache Resized (bytes)
    2009-08-02-23.28.53.629400+120 I1021152A485       LEVEL: Event
    PID     : 602270               TID  : 3342        PROC : db2sysc 0
    INSTANCE: db2mes               NODE : 000         DB   : MES
    APPHDL  : 0-8                  APPID: *LOCAL.DB2.090729131318
    AUTHID  : MESADM 
    EDUID   : 3342                 EDUNAME: db2stmm (MES) 0
    FUNCTION: DB2 UDB, config/install, sqlfLogUpdateCfgParam, probe:20
    CHANGE  : STMM CFG DB MES: "Pckcachesz" From: "1311" <automatic>  To: "1055" <automatic>
    2009-08-02-23.28.54.510395+120 I1021638A507       LEVEL: Info
    PID     : 602270               TID  : 3342        PROC : db2sysc 0
    INSTANCE: db2mes               NODE : 000         DB   : MES
    APPHDL  : 0-8                  APPID: *LOCAL.DB2.090729131318
    AUTHID  : MESADM 
    EDUID   : 3342                 EDUNAME: db2stmm (MES) 0
    FUNCTION: DB2 UDB, buffer pool services, sqlbAlterBufferPoolAct, probe:90
    MESSAGE : Altering bufferpool "IBMDEFAULTBP" From: "19552" <automatic> To:
              "15648" <automatic>
    2009-08-02-23.29.24.543188+120 I1022146A494       LEVEL: Event
    PID     : 602270               TID  : 3342        PROC : db2sysc 0
    INSTANCE: db2mes               NODE : 000         DB   : MES
    APPHDL  : 0-8                  APPID: *LOCAL.DB2.090729131318
    AUTHID  : MESADM 
    EDUID   : 3342                 EDUNAME: db2stmm (MES) 0
    FUNCTION: DB2 UDB, config/install, sqlfLogUpdateCfgParam, probe:20
    CHANGE  : STMM CFG DB MES: "Database_memory" From: "205060" <automatic>  To: "185520" <automatic>
    2009-08-02-23.29.54.555357+120 I1022641A483       LEVEL: Event
    PID     : 602270               TID  : 3342        PROC : db2sysc 0
    INSTANCE: db2mes               NODE : 000         DB   : MES
    APPHDL  : 0-8                  APPID: *LOCAL.DB2.090729131318
    AUTHID  : MESADM 
    EDUID   : 3342                 EDUNAME: db2stmm (MES) 0
    FUNCTION: DB2 UDB, config/install, sqlfLogUpdateCfgParam, probe:20
    CHANGE  : STMM CFG DB MES: "Locklist" From: "3552" <automatic>  To: "3392" <automatic>
    2009-08-02-23.29.54.559234+120 I1023125A545       LEVEL: Event
    PID     : 602270               TID  : 3342        PROC : db2sysc 0
    INSTANCE: db2mes               NODE : 000         DB   : MES
    APPHDL  : 0-8                  APPID: *LOCAL.DB2.090729131318
    AUTHID  : MESADM 
    EDUID   : 3342                 EDUNAME: db2stmm (MES) 0
    FUNCTION: DB2 UDB, access plan manager, sqlra_resize_pckcache, probe:150
    CHANGE  : APM : Package Cache : FROM "4191641" : TO "3937361" : success
    IMPACT  : None
    DATA #1 : String, 29 bytes
    Package Cache Resized (bytes)
    2009-08-02-23.29.54.560050+120 I1023671A484       LEVEL: Event
    PID     : 602270               TID  : 3342        PROC : db2sysc 0
    INSTANCE: db2mes               NODE : 000         DB   : MES
    APPHDL  : 0-8                  APPID: *LOCAL.DB2.090729131318
    AUTHID  : MESADM 
    EDUID   : 3342                 EDUNAME: db2stmm (MES) 0
    FUNCTION: DB2 UDB, config/install, sqlfLogUpdateCfgParam, probe:20
    CHANGE  : STMM CFG DB MES: "Pckcachesz" From: "1055" <automatic>  To: "991" <automatic>
    2009-08-02-23.29.55.097984+120 I1024156A507       LEVEL: Info
    PID     : 602270               TID  : 3342        PROC : db2sysc 0
    INSTANCE: db2mes               NODE : 000         DB   : MES
    APPHDL  : 0-8                  APPID: *LOCAL.DB2.090729131318
    AUTHID  : MESADM 
    EDUID   : 3342                 EDUNAME: db2stmm (MES) 0
    FUNCTION: DB2 UDB, buffer pool services, sqlbAlterBufferPoolAct, probe:90
    MESSAGE : Altering bufferpool "IBMDEFAULTBP" From: "15648" <automatic> To:
              "13914" <automatic>
    2009-08-02-23.30.25.137828+120 I1024664A494       LEVEL: Event
    PID     : 602270               TID  : 3342        PROC : db2sysc 0
    INSTANCE: db2mes               NODE : 000         DB   : MES
    APPHDL  : 0-8                  APPID: *LOCAL.DB2.090729131318
    AUTHID  : MESADM 
    EDUID   : 3342                 EDUNAME: db2stmm (MES) 0
    FUNCTION: DB2 UDB, config/install, sqlfLogUpdateCfgParam, probe:20
    CHANGE  : STMM CFG DB MES: "Database_memory" From: "185520" <automatic>  To: "176480" <automatic>
    2009-08-02-23.41.12.098793+120 I1025159A362       LEVEL: Warning
    PID     : 602270               TID  : 4114        PROC : db2sysc 0
    INSTANCE: db2mes               NODE : 000
    EDUID   : 4114                 EDUNAME: db2logmgr (MES) 0
    FUNCTION: DB2 UDB, data protection services, sqlpgArchiveLogFile, probe:3108
    MESSAGE : Started archive for log file S0001679.LOG.
    2009-08-02-23.41.13.334331+120 I1025522A422       LEVEL: Warning
    PID     : 602270               TID  : 4114        PROC : db2sysc 0
    INSTANCE: db2mes               NODE : 000
    EDUID   : 4114                 EDUNAME: db2logmgr (MES) 0
    FUNCTION: DB2 UDB, data protection services, sqlpgArchiveLogFile, probe:3180
    MESSAGE : Completed archive for log file S0001679.LOG to TSM chain 0 from
              /db2/MES/log_dir/NODE0000/.

  • Automatic archiving of db2diag.log

    Good Morning everyone,
    I have a question regarding the db2diag.log. After a couple of month this logfile could increase dramatically. In order to make root cause analysis easier I would like to archive the file every month and clean it up to get a better overview in it.
    Is there a possibility do to this via DB2 (Alertlog archiving) or should I realize this with a planned Batchjob every month.
    Greetings
    Marco

    Hello Marco,
    You can archive the db2diag.log using the db2diag tool. You can specify the -A or -archive <dirname> option:
    http://publib.boulder.ibm.com/infocenter/db2luw/v9r5/index.jsp?topic=/com.ibm.db2.luw.admin.cmd.doc/doc/r0011728.html
    -A | -archive dirName
    Archives a diagnostic log file. When this option is specified, all other options are ignored. If one or more file names are specified, each file is processed individually. A timestamp, in the format YYYY-MM-DD-hh.mm.ss, is appended to the file name.
    You can specify the name of the file and directory where it is to be archived. If the directory is not specified, the file is archived in the directory where the file is located and the directory name is extracted from the file name.
    If you specify a directory but no file name, the current directory is searched for the db2diag.log file. If found, the file will be archived in the specified directory. If the file is not found, the directory specified by the DIAGPATH configuration parameter is searched for the db2diag.log file. If found, it is archived in the directory specified.
    If you do not specify a file or a directory, the current directory is searched for the db2diag.log file. If found, it is archived in the current directory. If the file is not found, the directory specified by the DIAGPATH configuration parameter is searched for the db2diag.log file. If found, it is archived in the directory specified by the DIAGPATH configuration parameter.
    Regards,
    Adam Wilson
    SAP development Support

  • What is the current schedule for 6.1.2 and will it fix the Exchange transaction log issue in 6.1?

    Just spent the entire night with virtually no sleep with our firm's group of IT engineers trying to keep our Exchange system online due to massive transaction log growth. Confirmed the issue related to 6.1 calendar bug with Activesync. The workarounds are not practical for large groups of users who depend on their mobile devices for work. Our users have no way of knowing that they are causing an issue so the Apple guidance isnt terribly useful to communicate to 1000 users. When can we expect a resolution? The problem is only going to get worse as more and more users hit the bug. Does anyone know if the issue will resolve as soon as someone installs the 6.1.2 update, assuming that has the fix. Im not trying to bash anyone but this is a very serious problem in enterprise deployments.

    The update was released some time today. 6.1.2 appears to specifically fix the Exchange issue causing excess comms and logging issues. However, although the update is available i do not see the notification badge on the Settings icon. Is this controlled by Apple or is there a user setting i am missing somewhere? I would prefer that all users see the badge to expedite user action.

  • Config certificate and log issues

    I config certificate and use it to connect ipsec vpn ， I just config    
    jinan-neusoft(config)#ip domain-name neusoft.com
    jinan-neusoft(config)#crypto key generate rsa general-keys
    The name for the keys will be: jinan-neusoft.neusoft.com
    Choose the size of the key modulus in the range of 360 to 4096 for your
      General Purpose Keys. Choosing a key modulus greater than 512 may take
      a few minutes.
    How many bits in the modulus [512]:
    % Generating 512 bit RSA keys, keys will be non-exportable...
    [OK] (elapsed time was 0 seconds)
    jinan-neusoft(config)#
    Nov 16 01:05:44.435:  RSA key size needs to be atleast 768 bits for ssh version 2
    jinan-neusoft(config)#
    Nov 16 01:05:44.435: %SSH-5-ENABLED: SSH 1.5 has been enabled
    jinan-neusoft(config)#crypto pki trustpoint CA1
    jinan-neusoft(ca-trustpoint)# enrollment url http://59.44.43.217:80
    jinan-neusoft(ca-trustpoint)# revocation-check crl
    jinan-neusoft(ca-trustpoint)# rsakeypair DMVPN-SY-KEY
    jinan-neusoft(ca-trustpoint)# auto-enrol
    jinan-neusoft(config)#crypto pki authenticate CA1
    Certificate has the following attributes:
           Fingerprint MD5: D5F9D56B 4D9A4260 43F21D39 811D7AD5
          Fingerprint SHA1: 1E49B228 DD57F4DB 43DD2C2F 03870C18 840DA12A
    % Do you accept this certificate? [yes/no]: y
    Trustpoint CA certificate accepted.
    then I have log issues like below ，even I config auto-enroll , I don t get  certificate pending information  from my certificate server ，
    my device is C3925 and ios is c3900-universalk9-mz.SPA.151-4.M4.bin ，how to deal with it ，top players ， THX~~~~
    Nov 16 01:07:54.871: %PKI-6-CERTRENEWAUTO: Renewing the router certificate for trustpoint CA1
    Nov 16 01:07:54.951: %CRYPTO-6-AUTOGEN: Generated new 512 bit key pair
    Nov 16 01:07:55.115: CRYPTO_PKI:  Certificate Request Fingerprint MD5: 939AF8C1 854DDA90 8FE03058 5635468F
    Nov 16 01:07:55.115: CRYPTO_PKI:  Certificate Request Fingerprint SHA1: 50F869D2 C0814317 7EB2ECC9 90461F3A 353E7089
    Nov 16 01:07:55.119: %SYS-3-INVMEMINT: Invalid memory action (malloc) at interrupt level
    -Traceback= 5564384z 68B3034z 945A8D0z 6D05DF0z 6
    jinan-neusoft(config)#D05F70z 6D06B50z 6D07268z 6D43018z 6D25044z 6D1988Cz 6D4CCE0z 91F0154z 91F0CC4z 91F0DA4z 4ACB9F4z 4127784z
    Nov 16 01:07:55.119: %SYS-2-MALLOCFAIL: Memory allocation of 40 bytes failed from 0x6D05DEC, alignment 0
    Pool: Processor  Free: 731143916  Cause: Interrupt level allocation
    Alternate Pool: None  Free: 0  Cause: Interrupt level allocation
    -Process= "<interrupt level>", ipl= 3
    -Traceback= 5564384z 6892328z 68B3064z 945A8D0z 6D05DF0z 6D05F70z 6D06B50z 6D07268z 6D43018z 6D25044z 6D1988Cz 6D4CCE0z 91F0154z 91F0CC4z 91F0DA4z 4ACB9F4z
    Nov 16 01:07:55.119: %SYS-3-INVMEMINT: Invalid memory action (malloc) at interrupt level
    -Traceback= 5564384z 68B3034z 945A8D0z 6D05DF0z 6D05F70z 6D06B50z 6D07268z 6D4308Cz 6D25044z 6D1988Cz 6D4CCE0z 91F0154z 91F0CC4z 91F0DA4z 4ACB9F4z 4127784z
    jinan-neusoft(config)#
    Nov 16 01:08:09.719: %PKI-6-CERTRENEWAUTO: Renewing the router certificate for trustpoint CA1
    Nov 16 01:08:09.879: CRYPTO_PKI:  Certificate Request Fingerprint MD5: 939AF8C1 854DDA90 8FE03058 5635468F
    Nov 16 01:08:09.879: CRYPTO_PKI:  Certificate Request Fingerprint SHA1: 50F869D2 C0814317 7EB2ECC9 90461F3A 353E7089
    jinan-neusoft(config)#
    Nov 16 01:08:09.883: %SYS-3-INVMEMINT: Invalid memory action (malloc) at interrupt level
    -Traceback= 5564384z 68B3034z 945A8D0z 6D05DF0z 6D05F70z 6D06B50z 6D07268z 6D43018z 6D25044z 6D1988Cz 6D4CCE0z 91F0154z 91F0CC4z 91F0DA4z 4ACB9F4z 4127784z
    Nov 16 01:08:09.883: %SYS-3-INVMEMINT: Invalid memory action (malloc) at interrupt level
    -Traceback= 5564384z 68B3034z 945A8D0z 6D05DF0z 6D05F70z 6D06B50z 6D07268z 6D4308Cz 6D25044z 6D1988Cz 6D4CCE0z 91F0154z 91F0CC4z 91F0DA4z 4ACB9F4z 4127784z
    jinan-neusoft(config)# Nov 16 01:07:54.871: %PKI-6-CERTRENEWAUTO: Renewing the router certificate for trustpoint CA1
    Nov 16 01:07:54.951: %CRYPTO-6-AUTOGEN: Generated new 512 bit key pair
    Nov 16 01:07:55.115: CRYPTO_PKI:  Certificate Request Fingerprint MD5: 939AF8C1 854DDA90 8FE03058 5635468F
    Nov 16 01:07:55.115: CRYPTO_PKI:  Certificate Request Fingerprint SHA1: 50F869D2 C0814317 7EB2ECC9 90461F3A 353E7089
    Nov 16 01:07:55.119: %SYS-3-INVMEMINT: Invalid memory action (malloc) at interrupt level
    -Traceback= 5564384z 68B3034z 945A8D0z 6D05DF0z 6
    jinan-neusoft(config)#D05F70z 6D06B50z 6D07268z 6D43018z 6D25044z 6D1988Cz 6D4CCE0z 91F0154z 91F0CC4z 91F0DA4z 4ACB9F4z 4127784z
    Nov 16 01:07:55.119: %SYS-2-MALLOCFAIL: Memory allocation of 40 bytes failed from 0x6D05DEC, alignment 0
    Pool: Processor  Free: 731143916  Cause: Interrupt level allocation
    Alternate Pool: None  Free: 0  Cause: Interrupt level allocation
    -Process= "<interrupt level>", ipl= 3
    -Traceback= 5564384z 6892328z 68B3064z 945A8D0z 6D05DF0z 6D05F70z 6D06B50z 6D07268z 6D43018z 6D25044z 6D1988Cz 6D4CCE0z 91F0154z 91F0CC4z 91F0DA4z 4ACB9F4z
    Nov 16 01:07:55.119: %SYS-3-INVMEMINT: Invalid memory action (malloc) at interrupt level
    -Traceback= 5564384z 68B3034z 945A8D0z 6D05DF0z 6D05F70z 6D06B50z 6D07268z 6D4308Cz 6D25044z 6D1988Cz 6D4CCE0z 91F0154z 91F0CC4z 91F0DA4z 4ACB9F4z 4127784z
    jinan-neusoft(config)#
    Nov 16 01:08:09.719: %PKI-6-CERTRENEWAUTO: Renewing the router certificate for trustpoint CA1
    Nov 16 01:08:09.879: CRYPTO_PKI:  Certificate Request Fingerprint MD5: 939AF8C1 854DDA90 8FE03058 5635468F
    Nov 16 01:08:09.879: CRYPTO_PKI:  Certificate Request Fingerprint SHA1: 50F869D2 C0814317 7EB2ECC9 90461F3A 353E7089
    jinan-neusoft(config)#
    Nov 16 01:08:09.883: %SYS-3-INVMEMINT: Invalid memory action (malloc) at interrupt level
    -Traceback= 5564384z 68B3034z 945A8D0z 6D05DF0z 6D05F70z 6D06B50z 6D07268z 6D43018z 6D25044z 6D1988Cz 6D4CCE0z 91F0154z 91F0CC4z 91F0DA4z 4ACB9F4z 4127784z
    Nov 16 01:08:09.883: %SYS-3-INVMEMINT: Invalid memory action (malloc) at interrupt level
    -Traceback= 5564384z 68B3034z 945A8D0z 6D05DF0z 6D05F70z 6D06B50z 6D07268z 6D4308Cz 6D25044z 6D1988Cz 6D4CCE0z 91F0154z 91F0CC4z 91F0DA4z 4ACB9F4z 4127784z
    jinan-neusoft(config)#

    I do not have the answer but have exactly the same issue, looks as if it is a bug of some kind :
    Cisco CISCO3945-CHASSIS (revision 1.0) with C3900-SPE150/K9 with 980992K/67584K bytes of memory.
    Processor board ID FCZ163371P3
    6 FastEthernet interfaces
    3 Gigabit Ethernet interfaces
    1 terminal line
    1 Virtual Private Network (VPN) Module
    DRAM configuration is 72 bits wide with parity enabled.
    255K bytes of non-volatile configuration memory.
    250880K bytes of ATA System CompactFlash 0 (Read/Write)
    System image file is "flash0:c3900-universalk9-mz.SPA.151-4.M4.bin"
    Nov 16 07:37:16.611: CRYPTO_PKI: Signature Certificate Request Fingerprint MD5: 358FF778 7C2E66AE 895BF088 BF022442
    .Nov 16 07:37:16.615: CRYPTO_PKI: Signature Certificate Request Fingerprint SHA1: 5F7A4300 20B62132 83D08C6E 2D315DF4 51EFE94D
    .Nov 16 07:37:16.623: %SYS-3-INVMEMINT: Invalid memory action (malloc) at interrupt level
    -Traceback= 5564384z 68B3034z 945A8D0z 6D05DF0z 6D05F70z 6D06B50z 6D07268z 6D4308Cz 6D25044z 6D1988Cz 6D4CCE0z 91F0154z 91F0CC4z 91F0DA4z 4ACB9F4z 412
    7784z
    .Nov 16 07:37:16.623: %SYS-2-MALLOCFAIL: Memory allocation of 72 bytes failed from 0x6D05DEC, alignment 0
    Pool: Processor  Free: 704933204  Cause: Interrupt level allocation
    Alternate Pool: None  Free: 0  Cause: Interrupt level allocation
    -Process= "", ipl= 3
    -Traceback= 5564384z 6892328z 68B3064z 945A8D0z 6D05DF0z 6D05F70z 6D06B50z 6D07268z 6D4308Cz 6D25044z 6D1988Cz 6D4CCE0z 91F0154z 91F0CC4z 91F0DA4z 4AC
    B9F4z Nov 16 07:37:16.611: CRYPTO_PKI: Signature Certificate Request Fingerprint MD5: 358FF778 7C2E66AE 895BF088 BF022442
    .Nov 16 07:37:16.615: CRYPTO_PKI: Signature Certificate Request Fingerprint SHA1: 5F7A4300 20B62132 83D08C6E 2D315DF4 51EFE94D
    .Nov 16 07:37:16.623: %SYS-3-INVMEMINT: Invalid memory action (malloc) at interrupt level
    -Traceback= 5564384z 68B3034z 945A8D0z 6D05DF0z 6D05F70z 6D06B50z 6D07268z 6D4308Cz 6D25044z 6D1988Cz 6D4CCE0z 91F0154z 91F0CC4z 91F0DA4z 4ACB9F4z 412
    7784z
    .Nov 16 07:37:16.623: %SYS-2-MALLOCFAIL: Memory allocation of 72 bytes failed from 0x6D05DEC, alignment 0
    Pool: Processor  Free: 704933204  Cause: Interrupt level allocation
    Alternate Pool: None  Free: 0  Cause: Interrupt level allocation
    -Process= "", ipl= 3
    -Traceback= 5564384z 6892328z 68B3064z 945A8D0z 6D05DF0z 6D05F70z 6D06B50z 6D07268z 6D4308Cz 6D25044z 6D1988Cz 6D4CCE0z 91F0154z 91F0CC4z 91F0DA4z 4AC
    B9F4z

  • Reverse call log issue

    i keep getting an error when i try to do a reverse call lookup. it says try setting phone list view to "call log" but i don't have that option. It says if this option is unavailable this is a known but and we are working with RIM to correct the issue. If you require assitance accessing the phone list view settings or would like to be notified when a fix is available please use the Send Us Feedback option and indicate Reverse Call Log issue in message. But where is this send us feedback? I'm so confused. Anyone have this problem or know where I can get some help for it? Thanks again

    How did you reload the firmware? Did you backup the data and perform a reset using *#7370# before reloading? Try and reply.
    Nokia C7

  • RMAN BACKUPS AND ARCHIVED LOG ISSUES

    제품 : RMAN
    작성날짜 : 2004-02-17
    RMAN BACKUPS AND ARCHIVED LOG ISSUES
    =====================================
    Scenario #1:
    1)RMAN이 모든 archived log들을 삭제할 때 실패하는 경우.
    database는 두 개의 archive destination에 archive file을 생성한다.
    다음과 같은 스크립트를 수행하여 백업후에 archived redo logfile을 삭제한다.
    run {
    allocate channel c1 type 'sbt_tape';
    backup database;
    backup archivelog all delete input;
    Archived redo logfile 삭제 유무를 확인하기 위해 CROSSCHECK 수행시 다음과
    같은 메시지가 발생함.
    RMAN> change archivelog all crosscheck;
    RMAN-03022: compiling command: change
    RMAN-06158: validation succeeded for archived log
    RMAN-08514: archivelog filename=
    /oracle/arch/dest2/arcr_1_964.arc recid=19 stamp=368726072
    2) 원인분석
    이 문제는 에러가 아니다. RMAN은 여러 개의 arhive directory중 하나의
    directoy안에 있는 archived file들만 삭제한다. 그래서 나머지 directory안의
    archived log file들은 삭제되지 않고 남게 되는 것이다.
    3) 해결책
    RMAN이 강제로 모든 directory안의 archived log file들을 삭제하게 하기 위해서는
    여러 개의 채널을 할당하여 각 채널이 각 archive destination안의 archived file을
    백업하고 삭제하도록 해야 한다.
    이것은 아래와 같이 구현될 수 있다.
    run {
    allocate channel t1 type 'sbt_tape';
    allocate channel t2 type 'sbt_tape';
    backup
    archivelog like '/oracle/arch/dest1/%' channel t1 delete input
    archivelog like '/oracle/arch/dest2/%' channel t2 delete input;
    Scenario #2:
    1)RMAN이 archived log를 찾을 수 없어 백업이 실패하는 경우.
    이 시나리오에서 database를 incremental backup한다고 가정한다.
    이 경우 RMAN은 recover시 archived redo log대신에 incremental backup을 사용할
    수 있기 때문에 백업 후 모든 archived redo log를 삭제하기 위해 OS utility를 사용한다.
    그러나 다음 번 backup시 다음과 같은 Error를 만나게 된다.
    RMAN-6089: archive log NAME not found or out of sync with catalog
    2) 원인분석
    이 문제는 OS 명령을 사용하여 archived log를 삭제하였을 경우 발생한다. 이때 RMAN은
    archived log가 삭제되었다는 것을 알지 못한다. RMAN-6089는 RMAN이 OS 명령에 의해
    삭제된 archived log가 여전히 존재하다고 생각하고 백업하려고 시도하였을 때 발생하게 된다.
    3) 해결책
    가장 쉬운 해결책은 archived log를 백업할 때 DELETE INPUT option을 사용하는 것이다.
    예를 들면
    run {
    allocate channel c1 type 'sbt_tape';
    backup archivelog all delete input;
    두 번째로 가장 쉬운 해결책은 OS utility를 사용하여 archived log를 삭제한 후에
    다음과 같은 명령어를 RMAN prompt상에서 수행하는 것이다.
    RMAN>allocate channel for maintenance type disk;
    RMAN>change archivelog all crosscheck;
    Oracle 8.0:
         RMAN> change archivelog '/disk/path/archivelog_name' validate;
    Oracle 8i:
    RMAN> change archivelog all crosscheck ;
    Oracle 9i:
    RMAN> crosscheck archivelog all ;
    catalog의 COMPATIBLE 파라미터가 8.1.5이하로 설정되어 있으면 RMAN은 찾을 수 없는
    모든 archived log의 status를 "DELETED" 로 셋팅한다. 만약에 COMPATIBLE이 8.1.6이상으로
    설정되어 있으면 RMAN은 Repository에서 record를 삭제한다.

    Very strange, I issue following command in RMAN on both primary and standby machine, but it they don't delete the 1_55_758646076.dbf, I find in v$archived_log, this "/home/oracle/app/oracle/dataguard/1_55_758646076.dbf" had already been applied.
    RMAN> connect target /
    RMAN> CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON ALL STANDBY;
    old RMAN configuration parameters:
    CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON ALL STANDBY;
    new RMAN configuration parameters:
    CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON ALL STANDBY;
    new RMAN configuration parameters are successfully stored
    RMAN>
    ----------------------------------------------------------------------------------

  • Call log issue after upgrading to OS 10.3.1.158​1 from 10.2

    Dear all.
    I have update my BlackBerry 10 os to 10.3.1.1581 and to my surprise i find that the call log os restricted to about 150-200 call whereas it was almost unlimited in the previous 10.2 os .
    BlackBerry should issue a fix asap since this is such a basic features and necessity.
    I find myself in a very bad situation after upgrading.

    I have two call lors. One in the phone app, and one in the hub.
    I feel like the one in the phone app is quite short, but the one in the hub is unlimited.
    Do you confirm on your side?
    That being said, tracking more than 150 previous calls regularly is an extreme usage of the phone, I don't think the OS is made for that. I suggest you use a third party app that will be suited at tracking 200 phone calls a day.
    There are several that are free currently in BlackBerry World (the Free March section).
    The search box on top-right of this page is your true friend, and the public Knowledge Base too:

  • BULK INSERT into View w/ Instead Of Trigger - DML ERROR LOGGING Issue

    Oracle 10.2.0.4
    I cannot figure out why I cannot get bulk insert errors to aggregate and allow the insert to continue when bulk inserting into a view with an Instead of Trigger. Whether I use LOG ERRORS clause or I use SQL%BULK_EXCEPTIONS, the insert works until it hits the first exception and then exits.
    Here's what I'm doing:
    1. I'm bulk inserting into a view with an Instead of Trigger on it that performs the actual updating on the underlying table. This table is a child table with a foreign key constraint to a reference table containing the primary key. In the Instead of Trigger, it attempts to insert a record into the child table and I get the following exception: +5:37:55 ORA-02291: integrity constraint (FK_TEST_TABLE) violated - parent key not found+, which is expected, but the error should be logged in the table and the rest of the inserts should complete. Instead the bulk insert exits.
    2. If I change this to bulk insert into the underlying table directly, it works, all errors get put into the error logging table and the insert completes all non-exception records.
    Here's the "test" procedure I created to test my scenario:
    View: V_TEST_TABLE
    Underlying Table: TEST_TABLE
    PROCEDURE BulkTest
    IS
    TYPE remDataType IS TABLE of v_TEST_TABLE%ROWTYPE INDEX BY BINARY_INTEGER;
    varRemData remDataType;
    begin
    select /*+ DRIVING_SITE(r)*/ *
    BULK COLLECT INTO varRemData
    from TEST_TABLE@REMOTE_LINK
    where effectiveday < to_date('06/16/2012 04','mm/dd/yyyy hh24')
    and terminationday > to_date('06/14/2012 04','mm/dd/yyyy hh24');
    BEGIN
    FORALL idx IN varRemData.FIRST .. varRemData.LAST
    INSERT INTO v_TEST_TABLE VALUES varRemData(idx) LOG ERRORS INTO dbcompare.ERR$_TEST_TABLE ('INSERT') REJECT LIMIT UNLIMITED;
    EXCEPTION WHEN others THEN
    DBMS_OUTPUT.put_line('ErrorCode: '||SQLCODE);
    END;
    COMMIT;
    end;
    I've reviewed Oracle's documentation on both DML logging tools and neither has any restrictions (at least that I can see) that would prevent this from working correctly.
    Any help would be appreciated....
    Thanks,
    Steve

    Thanks, obviously this is my first post, I'm desperate to figure out why this won't work....
    This code I sent is only a test proc to try and troubleshoot the issue, the others with the debug statement is only to capture the insert failing and not aggregating the errors, that won't be in the real proc.....
    Thanks,
    Steve

  • Hard Drive filling up: SubmitDiagInfo, /private/var & log issues

    This topic is part question, part help for people I've seen having a similar problem in other threads. My issue is different enough from the other issues, that I wanted to post it as a separate topic.
    I've had about 24GB of available space for weeks now. I haven't downloaded any large files recently, nor created any myself.
    Suddenly I noticed the hard drive space decreasing. I went from 24GB, to 19GB, to 10GB, then 8, 5, 1.5... next thing I knew, it said I had 260MB available. This was within maybe two days, with a big ramp-down within a couple of hours this morning, while I was on a train, and not even connected to a network.
    I started getting error messages saying my hard drive was full; then, I got errors saying I didn't have enough application memory, and applications were being paused, and I would have to force quit them. Within about 5 minutes, I dropped from 1.5GB to 260MB.
    Thinking back, the last week or so, I remembered that sometimes when I came into my office in the morning, my Mac would be awake (I usually sleep it at the end of the day, and an error message would be displayed saying SubmitDiagInfo had crashed. I thought this might have something to do with it.
    I did some detective work in these forums. I checked Activity Monitor and the Console. Sure enough, SubmitDiagInfo was taking up a bunch of CPU time.
    The Console revealed I had a lot of Diagnostic Logs. I tried deleting them with the Console's Clear button, but it didn't seem to do anything. I checked with OmniDiskSweep, and sure enough, I had over 20GB of log files.
    At this point, my hard drive was so full, I had to force quit OmniDiskSweep. I used the Go To Folder command and entered /private/var/log - The Diagnostic Logs folder was nearly 20GB. I deleted it and emptied the trash immediately.
    I looked at the /private/var/vm folder and noticed it was also very large (10GB), but I had read elsewhere not to mess with this folder.
    From the console, I quit SubmitDiagInfo.
    I check my hard drive, and I'm suddenly back to 24GB free space.
    When I look again at /private/var/vm, and sure enough it is 5GB smaller.
    This is weird stuff, and I hope this description helps anyone else having this problem.
    What's interesting is, because the /private folder is invisible, you can't use it to calculate your disk space usage. For example, the folders on my drive had the following space usage:
    62.46GB34.53GB+22.96GB+4.78GB4.02GB = 128.75GB (plus a few "small" folders with maybe 300MB)
    Since the drive showed 159GB total space available, I couldn't figure out where the other 30GB was.
    Once I found /private/log, I could see it had 19.29GB:
    62.4634.53+22.96+4.78+4.0219.29 = 148.04 - ah, this makes more sense, but I'm still missing 10GB! So, I look at /private/vm, and boom, there is the extra 10.6GB hiding. All 159GB present and accounted for.
    The question I have is, of course, can anyone explain why this is happening, so I can prevent it from happening again?
    I hope someone finds this helpful.

    Thanks... that is helpful. I have Carbon Copy Cloner, not
    Super Duper, so I will keep that solution in mind.
    Do not, repeat do not, clone your current suspect hard drive
    to your CCC backup. That would defeat the purpose of having
    a good backup. I don't know if you can boot from you CCC
    backup. That would be a good test. I was able to boot from
    my SuperDuper backup and notice normal hard drive space.
    In the meantime, I ran the extended system test, and the
    computer passed.
    Mine with the growing hard drive passed every test I had plus
    the test Apple recommended. They were quick place the blame
    on a Virtual Windows XP Pro. I do not thing that was the
    problem. My normal Macintosh HD is usually about 52 GB
    and it was showing 110 GB used and I never could figure out
    what was hogging the hard drive.
    Good luck!

  • Change Log issues - Post Upgrade

    Hi Experts,
    We are in the process of Upgrading BW from 3.X to BI 7. As part of this we copied our existing Production system into the sand box and basis did the technical upgrade on the same (Sand Box). Later we ran some post upgrade Jobs as part of the SAP defined Upgrade Process.
    1) But after the upgrade i can notice that most of the ODS objects, doesn't have 'Change Log' table in the 'Information (Log/Status)' screen.
    2) Even when i try to view the change log content in Manage screen, it gives me a pop up to enter the change log table, instead of directly taking me to the selection screen.
    3) When i try to activate a request, even that fails with an SQL error 'SAPSQL_EMPTY_TABNAME'.
    Is there any process that has to be run to link the Older version change log tables to the corresponding ODSs after Upgrade?
    Has anyone come accross similar issues? If yes, how was it solved? All suggestions are invited.
    Thanks and Regards,
    Jay

    HI JayaPrasad,
    Chek the note : 1059171 which is related to Change log,
    I too faced this issue when upgraded to Bi7.0 on SP12, but as soon as SP13 is installed the issue is solved, so I suggest to go for SP 13 for upgrading to Bi7.0.
    Regards,
    Srinivas

  • Call log issue in nokia 5230

    Hi all,
    i am having an issue in call log in my nokia 5230. It is logging call details only for 15 days in spite of making selection for 30 days. I am surprise to see it , when 15 days option it not available in the list, how it is happening.
    I have reloaded the software twice from Nokia site & several times selection for 30 days call log is selected, but all in vain. Can anybody help??
    Thanks  & regards 

    How did you reload the firmware? Did you backup the data and perform a reset using *#7370# before reloading? Try and reply.
    Nokia C7

  • Materialized view logs issue

    We are having issues with the size of materialized view logs in one od the database. The size of the log table is around 32G. Will appreciate if somebody will help in explaining why it is having such a huge size and is not getting purged.
    At the same time the master table is having comparatively smaller size of 18G(did not check table fragmentation).
    Also, please help me in understanding what is required to be done for fixing this issue.
    SQL> select LOG_OWNER,MASTER,LOG_TABLE,LOG_TRIGGER,PRIMARY_KEY from dba_mview_logs where log_owner='MARTDATA' and MASTER='POLICY_CONFIGURATION';
    LOG_OWNER MASTER LOG_TABLE LOG_TRIGGER PRI
    MARTDATA POLICY_CONFIGURATION MLOG$_POLICY_CONFIGURATION NO
    SQL> select owner, segment_name, sum(bytes)/1024/1024 "SIZE in MB" from dba_segments where segment_name='POLICY_CONFIGURATION' and owner ='MARTDATA' group by owner, segment_name;
    OWNER SEGMENT_NAME SIZE in MB
    MARTDATA POLICY_CONFIGURATION 18458
    SQL> select owner, segment_name, sum(bytes)/1024/1024 "SIZE in MB" from dba_segments where segment_name='MLOG$_POLICY_CONFIGURATION' and owner ='MARTDATA' group by owner, segment_name;
    OWNER SEGMENT_NAME SIZE in MB
    MARTDATA MLOG$_POLICY_CONFIGURATION 32298
    Thanks

    Oracle automatically purges rows in the materialized view log when they are no longer needed. Because Oracle must wait for all dependent materialized views to refresh before purging rows from a materialized view log, unwanted situations can occur that cause a materialized view log to grow indefinitely when multiple materialized views are based on the same master table or master materialized view.
    For example, such situations can occur when more than one materialized view is based on a master table or master materialized view and one of the following conditions is true:
    Materialized view is not configured for automatic refreshes and has not been manually refreshed for a long time. OR
    Materialized view has an infrequent refresh interval, such as every year, etc
    You can also refresh the materialized views associated with the log so that Oracle can purge rows from the materialized view log.
    If a materialized view log needs to be purged manually for some reason a procedure called DBMS_MVEW.PURGE_LOG can be used.
    Edited by: user130038 on Sep 30, 2011 6:49 AM

  • 7.5 Standby apply log issue - Cold backup of standby

    We are in the process of migrating to 7.8 from 7.5 and have a 7.5 standby. Needed to test the time is takes to backup from the standby once we go-live on the 7.8 64bit server. Logs have been applied to the 7.5 standby for more than a month just fine prior to doing a "cold" backup test on the standby. Now the logs will not apply to the standby.
    ERR 20039 Log 
    Logrecovery is not allowed, because state of log volume is 'HistoryLost' (log must be cleared)
    2014-05-04 10:02:16 
    0xF28 WRN 20026 Admin
    Initialization of log for 'restore log' failed with 'LogAndDataIncompatible'
    First - backing up the standby in ADMIN mode / cold backup on the standby database, right?  The source and target (standby) have different server names.
    Is it possible to clear the log area or some other process to fix the issue?

    Hi Mike,
    You may need to restore the database with re-intialization and clear the logs
    Refer to the copy steps described in the thread
    Error while recover logs
    Hope this helps.
    Regards,
    Deepak Kori

Maybe you are looking for