jde client fail to start

[me2k]

Hello,
today jde started to fail during launching client application.
In client log i see:
<font class="small">Code:</font><hr /><pre>
1112/5668 Mon Apr 25 20:45:25 2011 jdb_ctl.c2763
Starting OneWorld

1112/5668 Mon Apr 25 20:45:32 2011 combined.c344
RDEL0000045 - Could not open tables for reliable event delivery (F90703 and F90704). Reliable event delivery will be disabled

1112/5668 Mon Apr 25 20:45:33 2011 Environment.cpp172
Solution Explorer Started

1112/5668 Mon Apr 25 20:45:34 2011 ODBC_U1.C964
ODB0000172 - Columns in Table F9000 not equal to specs
Column TMTASKID
Database Control Tables - Prod

1112/5668 Mon Apr 25 20:45:34 2011 JDBODBC.C1504
ODB0000055 - Describe table failed for table F9000.

1112/5668 Mon Apr 25 20:45:34 2011 jdb_drvm.c839
JDB9900168 - Failed to initialize db request

1112/5668 Mon Apr 25 20:45:34 2011 JTP_CM.C1088
JDB9909007 - Unable to obtain driver request handle

1112/5668 Mon Apr 25 20:45:34 2011 JTP_CM.C1088
JDB9909007 - Unable to obtain driver request handle
</pre><hr />

From server side:
<font class="small">Code:</font><hr /><pre>
2696/2764 Mon Apr 25 20:45:29 2011 IPCPUB.C3135
process 2696 <jdenet_n> registered in entry 12

2696/2764 Mon Apr 25 20:45:38 2011 NETRCV.C290
10054-Error from Host=<10.68.2.87> in recv returned 10054 (WSAECONNRESET): Connection was reset by peer
</pre><hr />

Can anybody help figure out what's wrong?

 

[cncjunior1]

You can try to delete your global table specs from your client and see if it will pull the correct ones in when you log in. Did you apply any ESU that would affect the F9000 or promote it to Production recently?

 

[me2k]

We did not do anything.
When we saw this problem, i stared figure out what wrong and I find that sql server is totaly run iut from hdd momory. I did purged some info. Not from jde base. But nothing changes...

 

[ebearman]

Did you try what cncjunior requested about deleting local specs?

 

[me2k]

<font class="small">Code:</font><hr /><pre>5164/5824 Tue Apr 26 06:43:20 2011 JDETAMIO.C286
TAM: tamfopen X:\B7\PD7333\spec\glbltbl.xdb error 3-The system cannot find the path specified. WinErrNum=3.

5164/5824 Tue Apr 26 06:43:20 2011 JDETAM.C423
TAMCreateIndexFile: Error creating index file : Cannot create a file when that file already exists. WinErrNum=183. No such file or directory. Std C errno=2. (X:\B7\PD7333\spec\glbltbl.xdb)

5164/5824 Tue Apr 26 06:43:20 2011 jdetamsp.c5247
Error creating GLBLTBL.XDB

5164/5824 Tue Apr 26 06:43:20 2011 JDETAMIO.C1299
TAMInitX: Error opening index file "x:\b7\pd7333\spec\gbrlink.xdb" : The system cannot find the path specified. WinErrNum=3. No such file or directory. Std C errno=2. (x:\b7\pd7333\spec\gbrlink.xdb) </pre><hr />



<font class="small">Code:</font><hr /><pre>5164/5824 Tue Apr 26 06:43:25 2011 jdb_rst.c1099
JDB9900307 - Failed to find table specifications

5164/5824 Tue Apr 26 06:43:25 2011 jdb_rq1.c1464
JDB3100007 - Failed to get valid table specifications

5164/5824 Tue Apr 26 06:43:25 2011 jdb_rst.c351
JDB9900915 - Failed to find global table specs. </pre><hr />


i try, have many errors like i post above.

 

[Softtop]

Me2k,

This is the important bit of information that was missing, if I understand you correctly, your SQL server ran out of disk space whilst extending your production databases? This has caused the database to corrupt and you are seeing this at login because F9000 has become corrupt.

You could copy the F9000 table from PY (if you use the promotion path for tasks) but this wont really solve your problem as you dont know what else has corrupted within the production databases. My advice would be to break out the last backup before the disk was full and restore that, you may loose some data but you could spend weeks trying to verify the integrity of the environment as it is now.

May I also suggest you invest in some server monitoring software so it can at least warn you before this happens again.

Regards

Pete

CNC/Developer

All releases, All platforms