• Introducing Dark Mode! Switch by clicking on the lightbulb icon next to Search or by clicking on Default style at the bottom left of the page!

Old JDE version, just noticed we lost access after June 2019.

Hello

I am contacting you because totally by chance, I noticed that our legacy (consult only) ERP is no longer accessible (I guess, as of 06/30/2019).

Changing dates on database/deployment server does not help.


I have no idea about JDE, jde.ini says B73.2.1

After some google research I saw something about BDSEC=ROBIN in this forum, but it seems to be for some other version of JDE and not mine.

Any chance we can get into our historic information again? (JDE database and client server are some super old computers that we managed to virtualize into ESXi, they are running winnt4.0. Then there is the client VM that runs windows server 2000, I have the same problem both on the deployment server and the client one)

Totally lost here :(
 

Attachments

JEMILLER

VIP Member
Hi,

You are correct that from XE/ERP 8 SP 17.1 and later that this in the JDE.INI should work:

[DB SYSTEM SETTINGS]
BDSEC=ROBIN


I believe that for B73.2.1 that this might work:

[DB SYSTEM SETTINGS]
BD=POOH
 
Hi,

You are correct that from XE/ERP 8 SP 17.1 and later that this in the JDE.INI should work:

[DB SYSTEM SETTINGS]
BDSEC=ROBIN


I believe that for B73.2.1 that this might work:

[DB SYSTEM SETTINGS]
BD=POOH
MMmm, addind that to JDE.ini (there is one in the JDE oracle database server, 2 in the deployment server, and in the app server there is one in winnt folder and one for each user), nets me this when i open oneworld explorer:
Anotación 2020-05-06 084444.jpg

Using the same user and password as for the normal application gets me nowhere.

There is also a db system - secondary section on most JDE.ini files, for some local database it seems.

---

If i change the date in the database and deployment servers, i can access oneworld explorer on the deployment server. Its not a solution, but some kind of workarround.
Too bad it does not work on the newer windows 2000 server that we use for accessing the info, becasue i can only get into de deployment server using vmware esxi console, and i dont know how to get files out of that old thing using the network (windows nt4.0 is kind of arcane for me).
 
Hi,

You are correct that from XE/ERP 8 SP 17.1 and later that this in the JDE.INI should work:

[DB SYSTEM SETTINGS]
BDSEC=ROBIN


I believe that for B73.2.1 that this might work:

[DB SYSTEM SETTINGS]
BD=POOH
i believe i answered this already, but i googled arround with BD=pooh and i saw i had to set the default password, and now it works!
 

JEMILLER

VIP Member
Yep, that was it. I should have elaborated. When you use the "backdoor" security mechanism it puts you into passthrough authentication to the database. That is, I believe it circumvents the JDE security server so you cannot use your JDE password. You need to be using a user id/password that is present on the backend database. I have a few old JDE historical systems running with clients were I put most of the data onto a readonly tablespace with only workfiles needed to run key reports left read/write. Depending on the client's security view they then either provisioned dedicated database user id's for each user needing to access the "archived" system or just went with a shared user id/password.
 
Yep, that was it. I should have elaborated. When you use the "backdoor" security mechanism it puts you into passthrough authentication to the database. That is, I believe it circumvents the JDE security server so you cannot use your JDE password. You need to be using a user id/password that is present on the backend database. I have a few old JDE historical systems running with clients were I put most of the data onto a readonly tablespace with only workfiles needed to run key reports left read/write. Depending on the client's security view they then either provisioned dedicated database user id's for each user needing to access the "archived" system or just went with a shared user id/password.
}

One more thing.

On a thread in this forum (where i saw about the robin thing), people were talking about their version (newer than mine but still old) working only until 2038.
I guess this applies for me too? (have to inform management)
 

JEMILLER

VIP Member
Interesting. I was not aware of a hard stop even for the BD setting in 2038. Maybe it is something else in the system that breaks by that time.

I would suggest that if your business believes they will need your historical JDE information 18 years from now that you just define the specific records retention policy and then extract the data into some tables or pre-printed reports. I know a lot of people would say "why would you need information 18 years later". For many businesses I can't think of a valid reason but with my background being partially in medical manufacturing I know that at least in that industry that you have to keep lot information and other data for the "life of the patient" that a device is implanted into. So that basically means forever.
 
Interesting. I was not aware of a hard stop even for the BD setting in 2038. Maybe it is something else in the system that breaks by that time.

I would suggest that if your business believes they will need your historical JDE information 18 years from now that you just define the specific records retention policy and then extract the data into some tables or pre-printed reports. I know a lot of people would say "why would you need information 18 years later". For many businesses I can't think of a valid reason but with my background being partially in medical manufacturing I know that at least in that industry that you have to keep lot information and other data for the "life of the patient" that a device is implanted into. So that basically means forever.
If i am not mistaken, its not a hard lock, but something about 32 bit dates not working past certain day in 2038, causing the application to crash.

I used to know about oracle database (not JDE) in previos jobs, but i know nothing currently (i kinda forgot).

The only remaining employee who knows how this JDE works will have to extract all the info (its financial stuff).
 
Top