Author Topic: error codes from arsdb  (Read 3289 times)

ibmarthin

  • Jr. Member
  • **
  • Posts: 68
    • View Profile
error codes from arsdb
« on: December 12, 2016, 02:38:03 AM »
Prior to upgrade I wanted to export the tables, but got an error 11 from arsdb which stopped exporting ..
Does anyone know where to look up error codes from arsdb. The "Messages and codes" did not help much.

arsdb -xv
mkdir /u/OD/backup950/PRODOD                                             
ARS4036I Exporting table PRODOD.arsag                                     
ARS4036I Exporting table PRODOD.arsag2fol                                 
ARS4036I Exporting table PRODOD.arsagfld                                 
ARS4036I Exporting table PRODOD.arsagfldalias                             
ARS4036I Exporting table PRODOD.arsagindex                               
ARS4036I Exporting table PRODOD.arsagperms                               
ARS4036I Exporting table PRODOD.arsann                                   
ARS4036I Exporting table PRODOD.arsapp                                   
ARS4036I Exporting table PRODOD.arsappusr                                 
ARS4036I Exporting table PRODOD.arscab                                   
ARS4036I Exporting table PRODOD.arscab2fol                               
ARS4036I Exporting table PRODOD.arscabnames                               
ARS4084E Unable to export table arscabnames.  err=11                     
arsdb: ARS4037E Unable to export table PRODOD.arscabnames                 
total 1752                                                               
-rw-r--r--   1 Z6IMN    STC         8573 Dec 11 01:01 PRODOD.arsag       
-rw-r--r--   1 Z6IMN    STC        32340 Dec 11 01:01 PRODOD.arsag2fol   
-rw-r--r--   1 Z6IMN    STC        55439 Dec 11 01:01 PRODOD.arsagfld     
-rw-r--r--   1 Z6IMN    STC         4027 Dec 11 01:01 PRODOD.arsagfldalias
-rw-r--r--   1 Z6IMN    STC          572 Dec 11 01:01 PRODOD.arsagindex   
-rw-r--r--   1 Z6IMN    STC        11418 Dec 11 01:01 PRODOD.arsagperms   
-rw-r--r--   1 Z6IMN    STC         1484 Dec 11 01:01 PRODOD.arsann         
-rw-r--r--   1 Z6IMN    STC       448119 Dec 11 01:01 PRODOD.arsapp         
-rw-r--r--   1 Z6IMN    STC         1520 Dec 11 01:01 PRODOD.arsappusr       
-rw-r--r--   1 Z6IMN    STC          496 Dec 11 01:01 PRODOD.arscab         
-rw-r--r--   1 Z6IMN    STC          268 Dec 11 01:01 PRODOD.arscab2fol     

Justin Derrick

  • IBM Content Manager OnDemand Consultant
  • Administrator
  • Hero Member
  • *****
  • Posts: 2229
  • CMOD Guru for hire...
    • View Profile
    • Tenacious Consulting
Re: error codes from arsdb
« Reply #1 on: December 12, 2016, 06:25:10 AM »
Use the -f ("force") option to force it to continue the process when it encounters errors.  Are you in the middle of an upgrade?  Because this error is expected when exporting database table after updating the CMOD software, but before you've issued the -u ("update") option.

-JD.
IBM CMOD Professional Services: http://TenaciousConsulting.com
Call:  +1-866-533-7742  or  eMail:  jd@justinderrick.com
IBM CMOD Wiki:  https://CMOD.wiki/
FREE IBM CMOD Education & Webinars:  https://CMOD.Training/

Interests: #AIX #Linux #Multiplatforms #DB2 #TSM #SP #Performance #Security #Audits #Customizing #Availability #HA #DR

Claudio Boscaini

  • Newbie
  • *
  • Posts: 2
  • I/T Specialist at IBM Italy
    • View Profile
Re: error codes from arsdb
« Reply #2 on: December 12, 2016, 07:38:24 AM »
Hello Marthin. If you are using the new CMOD libraries to export the existing tables, the -xv parameters will try to export all the tables that are known by the new version of CMOD.  arscabnames is a V9.5 table and so does not exist in your DB.  Either you export the single tables or you add the parameter that Justin Derrick has already posted to force the arsdb to continue its processing.

ibmarthin

  • Jr. Member
  • **
  • Posts: 68
    • View Profile
Re: error codes from arsdb
« Reply #3 on: December 13, 2016, 12:31:30 AM »
Thanks for the input.
I would have exported all tables, but ended up only to export the 7 effected by the upgrate to version 9.5
I was told explicitly by IBM always to use the new version of arsdb when upgrading, so I see I should have used the -f parameter to bypass non existent tables.

But the question was where to find error codes for arsdb which hopefully would have helped in the situation.

Justin Derrick

  • IBM Content Manager OnDemand Consultant
  • Administrator
  • Hero Member
  • *****
  • Posts: 2229
  • CMOD Guru for hire...
    • View Profile
    • Tenacious Consulting
Re: error codes from arsdb
« Reply #4 on: December 13, 2016, 07:23:48 AM »
Hi Marthin.

In this case, the error number could have come from a variety of places -- CMOD, DB2, or the operating system.  Sometimes finding a relevant error number takes some guesswork.  For CMOD, refer to the Messages and Codes manual inside the Knowledge Centers:  https://cmod.wiki/index.php?title=Main_Page#IBM_CMOD_Knowledge_Centers

DB2 also has two enormous Messages and Codes manuals.  On the UNIX platforms, OS-specific errors and brief descriptions can usually be found in a file called errno.h.  I'm not familiar with z/OS, but I'm sure there are manuals and files that can help you.

-JD.
« Last Edit: December 14, 2017, 10:51:18 AM by Justin Derrick »
IBM CMOD Professional Services: http://TenaciousConsulting.com
Call:  +1-866-533-7742  or  eMail:  jd@justinderrick.com
IBM CMOD Wiki:  https://CMOD.wiki/
FREE IBM CMOD Education & Webinars:  https://CMOD.Training/

Interests: #AIX #Linux #Multiplatforms #DB2 #TSM #SP #Performance #Security #Audits #Customizing #Availability #HA #DR

Ed_Arnold

  • Hero Member
  • *****
  • Posts: 1200
    • View Profile
Re: error codes from arsdb
« Reply #5 on: December 13, 2016, 01:54:01 PM »
Concur with what Justin says.

Error codes are always a source of frustration, even for us here in support, because they can come from almost anywhere.   :(

Ed

#zOS #ODF

ibmarthin

  • Jr. Member
  • **
  • Posts: 68
    • View Profile
Re: error codes from arsdb
« Reply #6 on: December 21, 2016, 07:04:34 AM »
ok - thanks anyway.
I just thought the "error number page" was missing in my book :)