ArcSDE 9.2 SP6 upgrade to ArcSDE 10 SP5 upgrade issue

[MilosMilicevic]

Hello,

I am having issues with upgrading to ArcSDE 10 SP5.
My gdb is on ArcSDE 9.2 SP6 on Oracle 10.2.0.3 x32 .I have migrated the data to Oracle 11.2.0.3 x64 (Server 2008 R2 x64), and trying to make a direct connection through ArcCatalog 10, in order to perform the upgrade to ArcSDE 10 SP5.


The problem that I encounter is that the direct connection will not work. It gives all sort of error messages (the most common one is a general DBMS error "underlying DBMS error [Unkonown error.No extended error.]".
We have installed the 32bit Oracle Client (full, not Instant), but avail.
I have followed the instructions on ESRI site, on how to connect without SDE service, eg: sde:oracle11g:<Net service name 32bit>
What is interesting is this: When i try to connect to the new database, from the old server, with ArcCatalog 9.2, it connects and shows all the data, but cannot upgrade, since it has ArcSDE 9.2 installed, and I cannot install a new version since that server still runs as a production server.

Please advise...
tnx in advance.
Regards,
Milos.

[MilosMilicevic]

Still no results.
Cannot create a direct connection, nor authenticate.
I tried to run the PostInstallation as an Administrator, as stated here :
http://forums.arcgis.com/threads/2972-ArcSDE-Repository-was-unsuccessfully-completed-empty-error-log but avail.

Does the authentication for v10 write the key to the registry, or into a table in the database (like 9.2, that writes into SDE.SERVER_CONFIG, if I am correct?) ?
I attached the value of the AUTH_KEY that is inside the UPDATED database...it still has old value. I suppose that this is because one of two reasons:

• Authorization was not able to update the property inside the SERVER_CONFIG.


• Authorization is supposed to write elsewhere - eg. registry.

If it writes to the registry, maybe I could create a registry key with the contents of the .ecp file I received from ESRI?


P.S.
I wrote this before I saw your post, Vince. Seems that we think alike 🙂
As you see, the key doesn't get updated in the db...
P.P.S.
Would an update statement to the SERVER_CONFIG AUTH_KEY make any difference?

[MarcoBoeringa]

Still no results.
Cannot create a direct connection, nor authenticate.

If, like seems the case here based on your SQL query result, the key still references the old 9.2 one, it isn't strange you can't connect.

Does the authentication for v10 write the key to the registry, or into a table in the database (like 9.2, that writes into SDE.SERVER_CONFIG, if I am correct?) ?

I think you answered this yourself by extracting it from the database using the SQL statement Vince supplied. It is clearly stored in the Server_Config table. I don't know if there is a secondary storage in registry, Vince undoubtedly can tell, but it seems highly unlikely to me to have dual storage here for an option like this.

If it writes to the registry, maybe I could create a registry key with the contents of the .ecp file I received from ESRI?

I think your better shot at this would be to use a SQL UPDATE statement to update the contents of the Server_Config table with the contents of the *.ecp file.

E.g. I expect it to look something like this:

sqlplus sde/password@instance
UPDATE server_config SET char_prop_value='arcsdeserver,100,ecpYOUR_ArcSDE10_CODE,none,YOUR_ArcSDE10_CODE' WHERE prop_name = 'AUTH_KEY';

I am not sure if the "none" is also included with full ArcSDE server licences, or replaced by something else, but my ArcSDE Personal licence that came with my ArcGIS for Home Use licence, displays "none" in between the ecp code and the final code if I look inside the table in SQL Server Management Studio. And yes, all values are concatenated in one comma separated string.

EDIT: I see the "None" is also included in the screenshot you posted of the faulty 9.2 authorization key in the Server_Config table of your installation, so it is also included with full ArcSDE server licences, so you can probably run the statement like above.

[MilosMilicevic]

That is what I hoped it can be done, but while looking at my .ecp file, I saw that theese licenses are for 10.1 !!!
It seems that out ESRi representative sent me wrong ECP code.
Or not?
Could I use the 10.1 licenses, or must I request new ones?!
Could this be the cause of my trouble!?

Tnx,
M.

P.S. Yes, none is for all licensses...at least the ones I have dealt with.

[MarcoBoeringa]

Could I use the 10.1 licenses, or must I request new ones?!

Good question, I can't tell. Codes may be - and likely are - tight to specific versions, but only a phone call to ESRI could tell. Clearly, the 9.2 code doesn't work with 10.0, so it probably is version tight and you may need to request a new one.

I don't think it would hurt though to run a SQL UPDATE statement and replace "101" with "100". In addition, if the *.ecp file is text, you might even edit that, and run it through the authorization process in the modified form. At worst, you replaced a bad key with another bad and non functional key.

Could this be the cause of my trouble!?

Well, having "101" where the authorization software maybe expects to read "100", is probably not going to help, although I am not sure if the authorization software even cares to process the ecp file to extract these individual values, or simply tries to run an UPDATE statement against the database (that somehow inexplicably fails than).

[MilosMilicevic]

I tried replacing the "101" string with the "100" in the license string, and updated the AUTH_KEY. Now I get following error when trying a direct connect:
No ArcSDE server license found.

I still cannot create the service.
When I try to pass the license string from the license file through sdesetup -o update_key, it says " no license found. Not licensed for Workgroup", which is correct, because my licenses are Enterprise Standard and Enterprise Basic.

It looks like that the licenses must be for exact version...
I will call my Esri representative, but I would like Vince's confirmation about this first...  🙂

Tnx,
M.

[MarcoBoeringa]

Seems to me it is time for that phone call to your ESRI representative to request the correct 10.0 Enterprise Standard key you need to get it up and running...

[VinceAngelo]

This reminds me of one of my most bizarre client calls:
"Do you remember installing ArcView four months ago?"
"Yes."
"We had a power outage, and now it isn't working.  Can you come fix it?"
After confirming the license manager won't start:
"What did you change?"
"Nothing."
An hour is spent working on the lm server...
"You must have changed something!"
"No, nothing."
Two more hours thrashing against the lm server...
"Are you sure you didn't change anything?"
"Positive."
Then someone else pipes up:
"Well, there was the one change, but it was months ago..."
Yup.  They edited the license file, changing all 3s to 1s, so they wouldn't
use as many seats.  It took that long to find it because the license was
only read on boot and, as a Unix box, the machine hadn't been rebooted
in the intervening months.  And the license manager wasn't reporting
an invalid key because they also changed the "3.0" LM version to an
undefined "1.0".

You cannot change anything in the license string without corrupting it. All the
different elements (product, version, expiration,...) are encoded into the key.
If anything is different, the key will not validate.  If the license is for the wrong
release, contact Customer Service to get the proper license file.

- V

[MarcoBoeringa]

This reminds me of one of my most bizarre client calls:
"Do you remember installing ArcView four months ago?"
"Yes."
"We had a power outage, and now it isn't working.  Can you come fix it?"
After confirming the license manager won't start:
"What did you change?"
"Nothing."
An hour is spent working on the lm server...
"You must have changed something!"
"No, nothing."
Two more hours thrashing against the lm server...
"Are you sure you didn't change anything?"
"Positive."
Then someone else pipes up:
"Well, there was the one change, but it was months ago..."
Yup.  They edited the license file, changing all 3s to 1s, so they wouldn't
use as many seats.  It took that long to find it because the license was
only read on boot and, as a Unix box, the machine hadn't been rebooted
in the intervening months.  And the license manager wasn't reporting
an invalid key because they also changed the "3.0" LM version to an
undefined "1.0".

:D:D:D

You cannot change anything in the license string without corrupting it. All the
different elements (product, version, expiration,...) are encoded into the key.
If anything is different, the key will not validate.  If the license is for the wrong
release, contact Customer Service to get the proper license file.

- V

Yup, sure, that was what I expected, but since I am neither an ESRI employee knowing all the nitty gritty details like you, nor the one who's handling this problem directly and thus can only give "remote help", you sometimes have to poke a little before you finally get somewhere and find out what is wrong. As you discovered then too after hours...

I hadn't really expected this to work. My last advice was to get that valid licence file from ESRI.

Congrats by the way with your 2000th post here on the forums~! 😉

[MilosMilicevic]

Got the 10.0 licenses, tried, and nothing changed.
When I try to authorize using sdestup, I get this>
ArcSdeServer license not found in license file(-8001). Error reading license information Error: (-8001) You are not licensed for SdeWorkGroup..
What does this mean? Is it possible that they gave me a wrong installation CD (Workgroup instead of Enterprise)?

M.

[MarcoBoeringa]

Got the 10.0 licenses, tried, and nothing changed.
When I try to authorize using sdestup, I get this>
ArcSdeServer license not found in license file(-8001). Error reading license information Error: (-8001) You are not licensed for SdeWorkGroup..
What does this mean? Is it possible that they gave me a wrong installation CD (Workgroup instead of Enterprise)?

M.

Might be, have you ever tried to log-in at the ESRI Customer Care portal? If you log in there with the proper credentials associated with your licences, there should be products available for download. You may be able to download the right version from there:

http://customers.esri.com/