The folks here did something similar - they actually had a second app / db
server and wanted to combine the oracle db.  They created a new user (ie
Aradmin2) and did an export and import of the data from the db they were
removing to the other db as that second user.  The ar.conf file was then
changed to use this aradmin2 db user and it worked well.  

 

I'm not sure I'd combine a dev or test with production, but in our case it
was two different non-production systems.

 

Not sure if I explained that clearly enough, but maybe it will give you an
approach to think about.

 

From: Action Request System discussion list(ARSList)
[mailto:[email protected]] On Behalf Of Hullule, Kiran
Sent: Friday, April 4, 2014 6:09 AM
To: [email protected]
Subject: Re: 2 Remedy Installation using same database

 

** 

This approach should work assuming that you have modified old server
references in ar.conf/armonitor.conf/arsystem startup script etc.  However
if you are pointing this new server towards same ARSystem tablespace that is
already been used by your development server then how are you going manage
with Server Name hard-code references in the development db?

However, you can use this newly built system like any other server group
system works sharing common database, hence I trust it should work by just
copying file system and modifying according to the new server name and
paths.

 

From: Action Request System discussion list(ARSList)
[mailto:[email protected]] On Behalf Of Ochavillo, Rafael John
Sent: 04 April 2014 13:36
To: [email protected] <mailto:[email protected]> 
Subject: 2 Remedy Installation using same database

 

** 

Hello Everyone,

 

I would just like to ask your help if my approach is possible in Remedy. 

 

I'm currently in the process of trying to make Remedy work on a Unix server.
What we did was to setup the server to have the same attributes as of the
current production. Copy all files, modify configuration files (ar.conf,
arsystem.lic, etc,) and the start-up script. Not really sure this will work
but we'd like to try. However, I don't have a test database to test with. So
my questions is that - would it be possible that I could point my test
Remedy to an Oracle DB that is already used by another Remedy instance
(development). I would just like to see if Remedy will work on that Unix
server without actually installing it.

 

My goal is quite ambitious and I'm not sure if it really works but I think
it's worth to try.

 

Any comments / suggestions ?

 

Thank you. :)

 

Regards,

Jojo Ochavillo

IT - Application Center of Excellence (ACE)

Support Tools Engineering Team

Office: (214) 567-0647

Email:  [email protected] <mailto:[email protected]> 

_ARSlist: "Where the Answers Are" and have been for 20 years_ 

_ARSlist: "Where the Answers Are" and have been for 20 years_ 


_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
"Where the Answers Are, and have been for 20 years"

Reply via email to