Repository Configuration

While configuring D7.1 repository, we are receiving below error message :-database we are using existing from D6.7 SP1 and its version is Oracle 11G

1. Copied the database schema (11G)

2. Mount the NAS

3. installed Content Server - Fine

4. Installed Doc Broker - Fine
5. Repository configuration got failed with below errors.

2014-04-03T20:20:15.866947 4881[4881] 0000000000000000 [DM_SESSION_I_INIT_BEGIN]info: "Initialize Distributed Content."

Last SQL statement executed by DB was:

#0 0x0000003c0f80f26e in waitpid () from /lib64/libpthread.so.0

#1 0x00000000009c3ecb in dmExceptionManager::WalkStack(dmException*, int, siginfo*, void*) ()

#2 0x00000000009c4308 in dmExceptionHandlerProc ()

#3 <signal handler called>

#4 0x00000000009ef8c0 in dmCryptoStore::GetAlgorithmID() const ()

#5 0x000000000080ad1d in addHeaderToPrivateKey(dmSession*, dmString, char*&) ()

#6 0x000000000080e3c9 in dmUpdatePrivateKeyStructure70(dmSession*, dmString) ()

#7 0x00000000008103ff in dmInitCryptoPrivateKey(dmSession*) ()

#8 0x00000000008a174c in dmInitDistributedContent(dmSession*) ()

#9 0x0000000000532b0a in dmCallInitProcs(dmSession*) ()

#10 0x0000000000540178 in dmStartUpDatabase(dmServerGlobalContext*, int) ()

#11 0x00000000004832c5 in dmRPCInit(char const*, char const*, int, char const*, dmServiceFailoverList&, dmObject&) ()

#12 0x0000000000486752 in dmRPCMain(int, char const**, dmBool, dmBool) ()

#13 0x0000000000487ead in main ()

Server exception handler: caught exception: Thu Apr 3 20:20:16 2014 Internal exception: Exception: 0 at (RPC Protected Failure)

We corrected entries in

Dm_server_Config_s .
dm_mount_point_S
dm_job_S
dm_location_S

Find more posts tagged with

Comments

Binay12

Couple of questions?

What do you mean used existing DB.? Are you trying to do an upgrade? If yes, you should do an upgrade not an fresh install as something has to trigger the database upgrade. There are very significant changes in 7.1 schema.

prasanna-fedex

what we are doing is

New Content Server - We are planning to install D7.1 on old database from 6.7 Sp1. so in configuration we select use existing ORACLE user account and database.

by this way, we are tring to upgrade the Content servers to 7.1.

Alvaro_de_Andres


prasanna-fedex wrote:

what we are doing is

New Content Server - We are planning to install D7.1 on old database from 6.7 Sp1. so in configuration we select use existing ORACLE user account and database.

by this way, we are tring to upgrade the Content servers to 7.1.

"Using existing ORACLE user account and database" means you don't provide SYSTEM oracle's account with the password (so the installer creates the user and schema), but a previously (BLANK) created user and schema.

If you want to upgrade an existing repository -> docbase configurator -> custom install -> upgrade existing repository

prasanna-fedex

I provided SYSTEM oracle account as well. the Content server is New -- so we have to select > Add New repository > Use an existing Oracle User account and Database. > Here we have inserted system user account and password and database user name and password.

rstein


the Content server is New -- so we have to select > Add New repository

You are not upgrading.


Use an existing Oracle User account and Database. > Here we have inserted system user account and password and database user name and password.

Don't do this, never.

If you want to upgrade an existing repository and are using a fresh D7.1 installation, you are doing wrong. Should copy existing (old) installation first and then upgrade. The installation guide has all the needed information in this regard.

If you don't want to upgrade, but install a new Content Server, setup a new (empty) repository, you should not copy schemas form the old system. Forget the old system if this is the case.

BinayGupta

As others have mentioned I am sure you must have got the point that with your steps you are not actually upgrading the repository. Where you are going wrong is when you select use existing database the installer uses the existing database (thinking its 7.1) and creates new 7.1 repository and the database upgrade scripts never executed on your database and quite likely this is the reason you are getting some DB error on repository start up.

Talking of the solution. What you can actually do is create new 7.1 Content Server > create new repository with a new database ofcourse with same name, id etc > once new 7.1 repository is created replace your new REP.ini file with the old 6.7 file and replace other imp files like aek etc. > run the server config again and select to upgrade repository.

Wondering is there a reason why you cannot follow the exact steps from Upgrade guide ?

prasanna-fedex

Hi Binay,

I am referring "

Upgrade and Migration Guide for version 7.0. I do not have upgrade and migretion guide for Version 7.1.

Also "where are Exact steps and in whcih guide ?

rchinchalkar1

Hi,

Can you advise if I want to Upgrade the OS of content server 7.2, how it can be done.

Current OS RHEL 6.0, I just want to install Content server on RHEL 7.0,

NO changed in DB server. It remains same.

what is the best possible approach for this.