Oracle ias/db problem.

[Steven E. Protter]

An application using forms 6.0.x works great client server.

Works great on HP-UX 11.00 32 bit
Oracle 8.1.7.0.0 32 bit.
ias 1.2.2 patch 12 (Includes forms and reports) 32 bit only. Also known as 9ias

Migrate it here:
HP-UX 11.11(11i) 64 bit.
Oracle 8.1.7.4.0
ias 1.2.2 patch 12 32 bit only certified for the platform.

When you start the application connecting to the new server after running a record querey based on list of values or any one of a hundred other database functions the app locks up.

The error code, if you are careful to watch is
FRM-92100, your connection to the database has been terminated.

The database trace sometimes picks up an ORA-0600 error, which means the same thing.

We hung a process trace using the tusc utility on the server and got lots of interesting results in this thread:

http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0x0a49b82b2d63d71190080090279cd0f9,00.html

Please take the time to read this thread carefully if you are going to make OS related suggestions(which I think is the issue). It includes the process traces and kmtune output and patch level information. Anything missing, ask for it I'll post it.

Question: has anybody encountered this problem on HP-UX 64 bit 11.11(11i)? If so, have they resolved it. If requested, I will post up init.ora tnsnames.ora and other configuration files.

The application runs on the web through the I.E. 5.5 browser running jinitiator 1.3.1.6

I'm just looking for the Oracle angle here. Os stuff should go to the other thread. Someone posted it up as an April success story because they thought it was a cool thread. If it wasn't my problem, I'd agree.

SEP

[Ramkumar Devanathan]

Hi Stephen,

I had been reading the thread and looking at the varied responses, had to point it out - it is not a success story but it is on the whole a good example of how many varied insights you get from the forum users... which I've pointed out to dan, although you haven't tasted much success till now. my sympathies are with you on that count.

- ramd.

[Steven E. Protter]

I think its a success because of the amount of resources brought to bear to solve a problem that effects multiple HP customers. It will be solved. I'm confident, I have almost as much ammunition to deal with this issue as the Pentagon. itrc has added tools to the hunt for a solution.

SEP

[Brian Crabtree]

Since you are looking for the Oracle angle =)

What changes were made between the two systems with Oracle besides the version (character set changes, etc)?

How was the database changed to the new version (offline backup, online backup with PITR, export/import)?

What is the ORA-00600 error posted?

Thanks,

Brian

[Steven E. Protter]

The only "changes" were the required database version upgrade. This was necessitated by problems converting the database data from 32 bit word size to 64 bit word size.

Not even the instance names were changed, though the tnsnames.ora and network files were changed to reflect the IP address of the new server.

SEP

[Steven E. Protter]

The ORA-600 was picked up by a database trace. the cool data on this issue is in the thread link in the original post.

SEP

[Brian Crabtree]

I dont see the actual ORA-00600 error message posted in the other side, that was what I was looking for. Also, have you considering tracing the database to look for what Oracle is doing at the time the process crashes. We have been having some problems with ORA-00600 [12333] that might be related to UTF8 character sets with different applications.

Regarding your word-size change, you did run the utlirp.sql script in ?/rdbms/admin to rebuild all of the scripts. This is not done as part of the migration as far as I know. (Just checking).

Also, it looks like your maxtsiz is a bit small from the kmtune report. Not sure how this would affect the 32bit IAS.

Thanks,

Brian

[Steven E. Protter]

Brian!

That's exactly what we're getting. !!!!

The funny part is we don't get it on the 11.00 32 bit servers.

Post a workaround or solution and earn a rabbit.

Please. The more details the better.

SEP

[Steven E. Protter]

Yeah, the word size conversion was successful. It only took two or three weeks to work the issues out.

We are certain it worked an we have no invalid objects on the database.

SEP

[Brian Crabtree]

Well, that's just it. We don't really know. The [12333] error is a network error, so Oracle goes as far as to say "This is a network error, you should fix that". We only see if on 8.1.7 64bit databases with UTF8. One option would be to change the character set to a non-utf8 (WE character set if possible) or move to 9i. The problem has always been intermittent.

As an FYI, one database that we were getting this error on we moved to WE8ISO8859P1 and the problem has not reoccured in the past two weeks (was about 1-2 times a day).

Hope this helps,

Brian