ezds.com : PPM Kintana - Triaging KNTA-10498 Internal Errors

Kintana - Triaging KNTA-10498 Internal Errors

NEW! Deploy Metrics v1.3

ZDS

Kintana Techniques

Kintana Internal Errors

The most common form is user's reporting Kintana internal error : 'Invalid username/password. Logon denied. (KNTA-10012)'

This usually involves nothing more than checking the user's record and possibly asking the user to clear his browser cache and close and reopen his browser.

The second form is rather tougher sledding

KNTA-10498 errors PPM Kintana Internal Error ORA_10403

How to read the error message

The Oracle error code : ORA-01403

The problem summary e.g.: no data found.

The Package : {KWFL_EXECUTION-2080}.
- This identifies the Kintana package in the schema, in this case KWFL_EXECUTION and
- The number following the dash is a tracking number locating the position in the function before the failure point.

(Optionally)Details on parameters, SQL code being executed, or other relevant information.

A trace back list of calls up to the failure point.

ORA-10498 Triage

The Kintana package identified may be the problem, but it's much more likely that the problem originates from your own SQL code that is being run by the Kintana function. This can be code in step source; stored procedures you have defined in the Kintana schema; or functions that these call in turn from packages stored in external database schemas.

If you want to do at least a first level triage before entering a Support Request, then the first place to look is at your own request data and step/package code.

I've listed below some of the basic reasons for these errors. In some cases this may be enough for you to locate and handle the problem for yourself. If not, having a basic handle of what the problem is should help you write up a more focussed support request.

The package names and numbers shown are just examples - the package specified in your error will be different.

ORA-00600

internal error code, arguments: [], [], [], [], [], [], [], [] {KCRT_REQUEST_DETAILS_TH-400} (KNTA-10498)

You might inspect the request and look for corrupted fields generally.

ORA-01000

maximum open cursors exceeded

A cursor is a pointer associated with a result set declared by a stored procedure. You will get this error if more cursors are in use than the number defined in the $ORACLE_HOME/network/admin/init.ora file. ITG recommend a minimum of 1000 cursors.

Use the scripts in Check #6 to get the maximum and used numbers of cursors.

If you have a reasonable margin, then increasing the maximum and restarting the database probably is'n going to help.

ORA-01002

fetch out of sequence {KWFL_EXECUTION-4020} (KNTA-10498)

This can happen if the code tries to fetch from a FOR UPDATE cursor after a commit.

Another way to generate an ORA-01002 error is to invalidate a cursor by rolling back to a savepoint that was set before the cursor was (implicitly or explicitly) opened. See Tom Kyte's article for more detail on this - and why an optimization in Oracle 10g may mask this problem.

ORA-01401

inserted value too large for column {KRSC_STAFF_PROFS_TH-600} (KNTA-10498)

This is our good old friend buffer overflow.

If you've updated step PL/SQL code recently, then check if fields used by the modified code are large enough.

In the case of requests, look for overlength fields. One work-around is to remove over-long text and attach it to the request.

ORA-01403

no data found {KWFL_EXECUTION-2080} (KNTA-10498)

The usual cause is that PL/SQL step or function code is trying to use an empty variable.

Check the request - are any fields empty? Perhaps a rule failed to fire or PL/SQL code that was supposed to set the field failed to update it, or set it to [NULL].

If you have added a new field to a request, then revisit requests submitted before the change and enter data in the new field if you have PL/SQL code in steps that access it.

When a PL/SQL execution step containing a rollback statement encounters an Oracle error, the rollback might rolls back core application processing. Issue a Savepoint at the start of the step.

ORA-04031

unable to allocate 23230 bytes of shared memory ("shared pool", or "large pool" ....") {KWFL_EXECUTION-7020} (KNTA-10498)

Have your DBA check the Large Pool, Shared Pool, and Java Pool size parameters in the $ORACLE_HOME/network/admin/init.ora file.

ORA-06502

PL/SQL: numeric or value error: character string buffer too small {FUNCTION_NNNN} (KNTA-10498)

Possible causes:

Notes and transaction history flags have been enabled on more than 40 fields in a Request Type.

The 5.0 'Configuring a Request Resolution System' manual (pp 136) notes:
PPM Kintana Field History Attributes

The request type could have too many statuses linked to it on the request Status tab. Note that any status with auto-link enabled will be linked to the request type.

ORA-06508

PL/SQL: could not find program unit being called {KWFL_WORKFLOW_ENGINE-8600} (KNTA-10498)

If the step source calls a function you have written, then check the schema of Kintana database to ensure that a package exists containing the function.

If your function does exist, but calls a function in an external database, then check the schema of that database to ensure the function exists, and check for connectivity problems to the external database. You can use Toad or Embarcadero to run the code directly to check this out.

Kintana™ and 'HP PPM (Project and Portfolio Management)'™ are trademarks of Hewlett Packard Corporation.