Codepage issue with 9.5

[jeffs42885]

First attempt at 9.5, getting the infamous error:

ARS4012E, unable to initialize the environment. The return code is 1

Windows 2008, Cache, Db2 10..What code page do I need to use? I cannot find anything on the web about it.

[Alessandro Perucchi]

Hello :-)

you were trying to do a arsdb -c ?

could you give us a bit more context?

Thanks!

[jeffs42885]

Whoops-

arsdb -u -I <OD_INSTANCE>

[jeffs42885]

Here is where I am at:

Procedure
To create the database:
1. Create the Content Manager OnDemand system tables with the ARSDB
program.
The ARSDB program is installed in the \Program Files\IBM\OnDemand\V9.5\
bin directory. Use the format: arsdb -I OnDemandInstanceName
-rtvOnDemandInstanceName is the name of the Content Manager OnDemand
instance. For example, ARCHIVE (see “Configuring instances on Windows” on
page 190).
Note: The Configurator will offer to create the database at the end of the
instance creation if database engine is DB2 and SQL server is installed

I ran that and heres the output:

ARS4015I Starting the DB2 JEFF database instance
ARS4078I The JEFF instance has already been started
ARS4018I Creating the DB2 JEFF database
ARS4062I Database created with territory 'US', code page '1208', code set 'UTF-8' and collating sequence ''
ARS4068I Updating the JEFF database configuration
ARS4073I Deactivating database JEFF
ARS4071I Backing up the JEFF database so that the updates can take effect
ARS4058E Unable to backup database JEFF.  err=-5099
arsdb:   ARS4019E Unable to create the DB2 JEFF database

[Karole]

What is your Windows Event Viewer reporting?

[jeffs42885]

Not seeing any errors related to this.

[Karole]

Hmm... is your db2diag.log showing anything interesting?   
Can you try the following?
Please first make sure, that DB2 is running by using the following
command:
"db2 connect to archive"
 
If the DB2 is down, please start it.
If the DB2 is running, please use the following command to start OD
 
"./arssockd -I archive -S"

[jeffs42885]

Thanks Karole. DB2 is indeed up

Heres my output:

db2 => connect to jeff
SQL5099N  The value "c:\arsdbpri\" indicated by the database configuration
parameter "NEWLOGPATH" is not valid, reason code "4".  SQLSTATE=08004
db2 =>

[Karole]

Let's try running

get db config for "od_instance",

to verify the path to db and log files.  Then check the file system to see if they're matched

[jeffs42885]

Perfect. Thank you Karole. That returned what appears to be a ton of useful information. Where should I look to compare apples to apples.

[jeffs42885]

Greetings all, with the help of IBM Support, we were able to resolve this. Here's what I ended up doing.

Upgrading to Fixpack 9.5.0.2
update db cfg for "InstanceName" using NEWLOGPATH NULL
proceeded with arsdb commands and creating the system log/load
fired up arssockd
logged in
did a happy dance

Shout to the support folks at IBM for helping me!

[Justin Derrick]

Ah yeah, I've seen this before on the UNIX/Linux versions -- something in the -c (create) or -u (update) breaks the logging in DB2, and it can't activate the database.

I suggest that everyone spends some time reading up on how your database does logging to gain a deeper understanding of how to configure and use them, as well as the features and functionality of each method.  Not being able to restore transaction logs after a database restore is a critical failure, so it needs to be tested and re-tested regularly to make sure backups are complete and usable.