Indexing problem?

From: John <john.gable_at_cedar.com>
Date: 12 Apr 2003 09:41:24 -0700
Message-ID: <e47c36e4.0304120841.3083d2bf_at_posting.google.com>


Hello,

I am a PeopleSoft developer working with a PeopleSoft application on an Oracle 8i 8.1.7.0.0 database and am experiencing a few serious problems that I think may be related. I apologize if this isn't the exact right forum for this question. Because I'm having this problem on a database which is a copy of another database in which I'm not experiencing this problem makes me think that there's something at the db level causing this.

There seems to be a date recognition problem. I'll try to explain my 2 symptoms in non-PeopleSoft-speak.

  1. Through the on-line system, I am able to update the current row (based on the current date) of an effective dated table without being signed in in the required "Correction" mode
  2. A PeopleSoft built-in function whose purpose is to return the effective date of the current row in the buffer is instead returning the effective date of the OLDEST row.

As I had mentioned, these same functions are working on the database from which the problematic database was copied. Here is what I've done so far in my troubleshooting:

  • Verified System Date
  • Dropped indexes and accessed data without them
  • Verified that the Oracle patch #869177 for descending indexes required for my PeopleSoft upgrade was applied

I thought that the problem was related to either indexes or db configuration but dropping the indexes of the table didn't seem to help.

Has anyone encountered similar issues or have any thoughts?

Thank you!

John Received on Sat Apr 12 2003 - 18:41:24 CEST

Original text of this message