James / John,
I should clarify, the fear is not for cross communication between
tablespaces - Oracle & ARS handle that well. The concern is if the
database SID names are the same, but refer to different oracle
instances. If there was a tnsnames.ora copy / overwrite snafu, you
could have both ARS instances talking to one Oracle instance and not
even know it (If this is in fact what is meant by "the DB is the same
name").
In thinking about what could be referencing the old ars server that the
installer would care about, I could only think of SERVER_CACHE left over
from ARS < v5 or a copied .lic file. Table fields & filter guides would
not affect the upgrade installer I hope. I can't think of other
embedded server references.
I've never encountered the installer upgrade option complaining that
the database intact and accessible - that seems very wrong - so I'm left
to conclude that the database being present & accessible is not the root
problem.
I _suspect_ that the installer detects that the ARS database it is about
to upgrade is in use by another running ARS server elsewhere - which
could easily happen if your SID's were the same in dev & prod.
The other problem here could be that all of the oracle binaries and
config files were copied, including tnsnames which refernces the prod
instance - and it is actually Oracle generating this error message. If
this is the case, the DBA will need to either:
A:) ensure that all references to the old db server hostname/ip in _any_
Oracle configurations are updated to the dev database hostname/ip
Or
B:) erase the instance and re-create it via standard tools/processes,
then export the data from prod and import it in dev.
Option B would be highly reccommended - who knows where Oracle stuffs
away information about where it is supposed to reside.
-brian luke
________________________________
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of McKenzie, James J C-E LCMC
HQISEC/L3
Sent: Tuesday, September 05, 2006 2:28 PM
To: arslist@ARSLIST.ORG
Subject: Re: Setup Dev Server
**
Brian:
Why the fear? If you name one tablespace ARSYSTEM for instance, and the
second ARSYSTEM1, there should be NO cross-talk between the two
tablespaces. The problem here might be that the database was physically
copied from one server to another and there may be internal checking
that is failing and thus the error.
James McKenzie
-----Original Message-----
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Luke, Brian
Sent: Tuesday, September 05, 2006 2:10 PM
To: arslist@ARSLIST.ORG
Subject: Re: Setup Dev Server
John,
By "the DB is the same name" do you mean the ORACLE SID or the database
server hostname?
With Oracle, the Db-name: ar.cfg parameter is used for the tablespace
name if it is not ARSYSTEM.
One thing that worries me about this config is that if the SID's are the
same, the only place they are differentiated is in tnsnames.ora - the
danger of unintended cross communication seems great.
What version of ARS have and are you upgrading from (this last time, and
tracing back?) Check the contents of SERVER_CACHE and see if there are
references to old servers there.
Also, did you copy the file containing the ARS licenses to the dev ARS
server? - try renaming it if you did.
One Oracle instance can have one or many tablespaces. Each tablespace
can contain the objects for one or more accounts/schemas and keep them
separate (even with the same table names).
-Brian Luke
-----Original Message-----
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of John Kelley
Sent: Friday, September 01, 2006 8:31 AM
To: arslist@ARSLIST.ORG
Subject: Setup Dev Server
Hi List: First time emailer. Long time reader.
I'm trying to setup our Dev Box(Windows 2003sp1) with AR 6.3. Having
errors upgrading an existing DB.
We took a copy of production DB, and placed it on a different oracle
Server. Oracle 9.2.0.4.0 64bit.
My tnsnames is set correctly to Dev Server and connection to remedb
listener.
The name of the DB is the same for Production and Dev. Which is OK.
They are on different servers.
When I'm setting up the Dev server running server.exe, Its asks for SID
name and what type of install. Upgrade, Overwrite or Shared. I select
Upgrade because the DB out there is an exact copy of the Production
having all the Data - I want the data in tact just to install the
Server.
Here is the Error
15:40:39 An error was encountered during the upgrade of the AR System
database.
15:40:39 Installation terminating ... Original database server is intact
and accessible
15:40:39 Resolve the problem that causes the error (contact Technical
Support, if necessary) 15:40:40 ****->[ShowMsg]: Setup is rolling back
directories....
15:40:40 Setup is rolling back the directories.
15:40:41 ServiceName not found. Using Default: Remedy Action Request
System Server
15:40:41 ****->[ERROR]: AR System Database upgrade error. The original
database is intact and accessible.
Anyboby have something similar. Or suggestion.
John Kelley
Help Desk Analyst
130 Royall Street
Canton, MA 02021
Mail Center 1W
781-737-3564
________________________________________________________________________
_______
UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org
________________________________________________________________________
_______
UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org
__20060125_______________________This posting was submitted with HTML in
it___
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org
