SQL HELP!!!

Toni_Nanneman

Active Member
OW b7322 sp12.2 SQL 6.5 hotfix 423

We have a 'suspect' JDE sql database and cannot connect to Central Objects.
Has anyone out there, ever had this before? Do you know the cause?
Resolution?

We're working with Microsoft but wanted to see if anyone has had a similar
experience!

By the way, I'd rather just pass on the comments about upgrading, et al,
it's in the works but right now I have to address this very urgent issue!


Toni Nanneman
CNC Administrator
503-370-7071 x7262
[email protected]
 

SSAJAROFF

Reputable Poster
Toni :

It usually happens if you move your DAT files (while SQL services are down)
to some other
directory.
You need to move these DAT files to the original location.
If you can't solve it that way, you have to restore JDE base from a clean
backup.

Sebastian


-----Mensaje original-----
De: Toni Nanneman [mailto:[email protected]]
Enviado el: Wednesday, January 24, 2001 8:06 PM
Para: [email protected]
Asunto: SQL HELP!!! ~~0:4544


OW b7322 sp12.2 SQL 6.5 hotfix 423

We have a 'suspect' JDE sql database and cannot connect to Central Objects.
Has anyone out there, ever had this before? Do you know the cause?
Resolution?

We're working with Microsoft but wanted to see if anyone has had a similar
experience!

By the way, I'd rather just pass on the comments about upgrading, et al,
it's in the works but right now I have to address this very urgent issue!


Toni Nanneman
CNC Administrator
503-370-7071 x7262
[email protected]




--------------------------
To view this thread, visit the JDEList forum at:
http://198.144.193.139/cgi-bin/wwwthreads/showflat.pl?Cat=0&Board=OW&Number=
4544
*************************************************************
This is the JDEList One World / XE Mailing List.
Archives and information on how to SUBSCRIBE, and
UNSUBSCRIBE can be found at http://www.JDELIST.com
*************************************************************
 

Adrian_Chimirel

Legendary Poster
Toni,
If restoring is not an option you'll have it the hard way: the Customer Support from Microsoft and I had to rebuilt the broken index pages; there weren't but five or six and it took only one day! MS explanation was that the Sys Admin installed the Backup Exe swre without putting the JDE services & SQL Server down; once the installation finished, it rebooted the ES ...
Good luck,
Adrian Chimirel

LIVE: B732.1 SP12.2, Oracle 805
SANDBOX: XE SP3, 8i
RS/6000, Citrix, 200+ clients
 

misenberg

Member
Toni,

I have seen many suspect databases. There is a query you can run to
unsuspect it. The problem is this: You need to know the cause. The cause
could be because you did not expand your data device, your log device OR
your TEMPBD in SQL 6.5. which will cause this to happen. The worst is you
may need to restore from tape. Here is the query you need to run. Also
make sure your configuration parameters are set correctly. Like
OpenObjects, etc... There is a whole list for SQL 6.5 on performance tuning
which really means making it run correctly. Above all make sure you do not
put TEMPDB in RAM.

Do the following: Open ISQL open folder Install and open file instsupl.sql
RUN query
This creates a stored procedure called sp_resetstatus
In ISQL from the master device run sp_resetstatus (database name that is
suspect)

This will restore the status and make the database accessible if it is not
totally corrupt. Once on line do not use the database until you fix the
problem. Check for the space available on all the devices.

Good Luck
 
Discover how to build no-code data integrations and business process automations.

rafaelrv

Member
The first step is that you check that your ODBC's are running the test
tools, that came with the configuration option (at the end of
configuration).


----- Original Message -----
From: Toni Nanneman <[email protected]>
To: <[email protected]>
Sent: Wednesday, January 24, 2001 5:05 PM
Subject: SQL HELP!!! ~~0:4544


> OW b7322 sp12.2 SQL 6.5 hotfix 423
>
> We have a 'suspect' JDE sql database and cannot connect to Central
Objects.
> Has anyone out there, ever had this before? Do you know the cause?
> Resolution?
>
> We're working with Microsoft but wanted to see if anyone has had a similar
> experience!
>
> By the way, I'd rather just pass on the comments about upgrading, et al,
> it's in the works but right now I have to address this very urgent issue!
>
>
> Toni Nanneman
> CNC Administrator
> 503-370-7071 x7262
> [email protected]
>
>
>
>
> --------------------------
> To view this thread, visit the JDEList forum at:
>
http://198.144.193.139/cgi-bin/wwwthreads/showflat.pl?Cat=0&Board=OW&Number=
4544
> *************************************************************
> This is the JDEList One World / XE Mailing List.
> Archives and information on how to SUBSCRIBE, and
> UNSUBSCRIBE can be found at http://www.JDELIST.com
> *************************************************************
 

Toni_Nanneman

Active Member
Thank you list for all your constructive comments and suggestions. We did
not lose our database but had a failed transaction log. Our network admin,
known from this point forward as Superman, worked with Microsoft to clean
this up and the database came back to life fully intact!

I'm keeping my fingers crossed for a 'good day'. Thanks again!
 
Top