Author Topic: ARS_ORIGINAL_CODEPAGE going from 8.4 to 8.5  (Read 4809 times)

jeffs42885

  • Guest
ARS_ORIGINAL_CODEPAGE going from 8.4 to 8.5
« on: March 27, 2012, 11:16:31 AM »
Hi All,

we are receiving this error after upgrading our stage server to 8.5 from 8.4

arsuser@stageserver[/home/arsuser/scripts]>Start_OD.sh
Password:
DB Error: STARTUP -- SQLSTATE=1. ARS_ORIGINAL_CODEPAGE is not defined in ars.cfg. Run arsdb -u -I dbinstance to determine setting of ARS_ORIGINAL_CODEPAGE, SQLCODE=0, File=arssrvr.c, Line=8432
arsuser@stageserver[/home/arsuser/scripts]>arsdb -u -I dbinstance
arsdb: Unable to load >DB2<

Has anyone experienced this error?

Ed_Arnold

  • Hero Member
  • *****
  • Posts: 1208
    • View Profile
Re: ARS_ORIGINAL_CODEPAGE going from 8.4 to 8.5
« Reply #1 on: March 27, 2012, 12:31:34 PM »
Hi Jeff - see if this helps, lots of doc on what you're seeing:

https://www-304.ibm.com/support/docview.wss?uid=swg27020591

Ed

#zOS #ODF

Justin Derrick

  • IBM Content Manager OnDemand Consultant
  • Administrator
  • Hero Member
  • *****
  • Posts: 2231
  • CMOD Guru for hire...
    • View Profile
    • Tenacious Consulting
Re: ARS_ORIGINAL_CODEPAGE going from 8.4 to 8.5
« Reply #2 on: March 27, 2012, 12:33:04 PM »
It's in the ReadMe for 8.5:

 4.1   New ars.cfg parameter ARS_ORIGINAL_CODEPAGE
        A new ars.cfg parameter, ARS_ORIGINAL_CODEPAGE, is now required.
        When using OnDemand for MP V8.5 to access a pre-V8.5 OnDemand instance,
        this MUST be set to the codepage the pre-V8.5 OnDemand server was
        running in.  Failure to set it will prevent the OnDemand server from
        starting.  Setting it incorrectly will result in data corruption.

        Example failure to start message which will be sent to the console:
         DB Error: STARTUP -- SQLSTATE=1.  ARS_ORIGINAL_CODEPAGE is not
                   defined in ars.cfg.  Run arsdb -u -I <OD_INSTANCE> to
                   determine setting of ARS_ORIGINAL_CODEPAGE, SQLCODE=0,
                   File=arssrvr.c, Line=7892

4.2   Steps to set the value of ARS_ORIGINAL_CODEPAGE
  4.2.1   UNIX Servers
        Run arsdb -u without ARS_ORIGINAL_CODEPAGE in the ars.cfg for
        information on the proper setting for ARS_ORIGINAL_CODEPAGE.

        An example of running the arsdb -u -I <OD_INSTANCE> command without
        ARS_ORIGINAL_CODEPAGE in the ars.cfg is:
          arsdb:  Unable to initialize environment. The return code is -1.  If
                  this is a new (created in 8.5) instance, then define
                  ARS_ORIGINAL_CODEPAGE=819 in ars.cfg.  Otherwise, if this is
                  an existing instance (created prior to 8.5), then define
                  ARS_ORIGINAL_CODEPAGE=923 in ars.cfg.  Once set,
                  ARS_ORIGINAL_CODEPAGE must never change.


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

jeffs42885

  • Guest
Re: ARS_ORIGINAL_CODEPAGE going from 8.4 to 8.5
« Reply #3 on: March 27, 2012, 12:49:20 PM »
Thanks for the feedback

This is an error message that we are getting with this:

arsuser@stageserver[/home/arsuser/scripts]>arsdb -u -I dbinstance
arsdb: Unable to load >DB2<

Justin Derrick

  • IBM Content Manager OnDemand Consultant
  • Administrator
  • Hero Member
  • *****
  • Posts: 2231
  • CMOD Guru for hire...
    • View Profile
    • Tenacious Consulting
Re: ARS_ORIGINAL_CODEPAGE going from 8.4 to 8.5
« Reply #4 on: March 28, 2012, 04:46:29 AM »
arsdb: Unable to load >DB2<

Looks like you upgraded DB2 but didn't run 'db2ln' to create links to the new DB2 libraries.

-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