FMS logs "ORA-04098: trigger 'SYS.XDB_PI_TRIG' is invalid and failed re-validation" (4324680)

Chatta subito con l'assistenza

Ottieni assistenza in tempo reale
Completa la registrazione

Accedi

Richiedi prezzo

Contatta il supporto vendite

Restituisci

Feedback inviato

Questo articolo ti è servito per risolvere il problema?

Seleziona valutazione

Titolo

FMS logs "ORA-04098: trigger 'SYS.XDB_PI_TRIG' is invalid and failed re-validation"
Descrizione

We're trying to determine why we see these messages in our Foglight Management Server (FMS) logs:

An error occurred while truncating table obs_metric_scalar_0108: java.lang.RuntimeException: java.sql.SQLException: ORA-04098: trigger 'SYS.XDB_PI_TRIG' is invalid and failed re-validation"
Causa

This issue is due to the Oracle setup. Foglight is just trying to truncate one of its own tables and the Oracle DDL triggers are interfering.

Appears that someone may have mistakenly installed in the SYS schema by performing the Foglight script installations as user SYS rather user Foglight. When Foglight was installed, the first two scripts are run a user 'sys', then remaining two run as user 'foglight.
NOTE: These of course wipe out any existing database as they reinitialize/create the database.

USER 'SYS'
<foglight_home>/scripts/sql/oracle_drop_db.sql
<foglight_home>/scripts/sql/oracle_create_db.sql

USER 'FOGLIGHT'
<foglight_home>/scripts/sql/oracle_create_schema.sql
<foglight_home>/scripts/sql/oracle_populate_db.sql
Risoluzione

Suggested resolution was to remove the Foglight installation and perform the correct steps to initialize/populate the back-end database. Some of the configuration can be saved by exporting before removing the FMS installation, then importing this information into the new installation.
One can export any custom dashboards, rules, registry variables before performing the uninstall, then reimport the exported text files. Exporting custom dashboards SOL39370
Below is an example procedure where I modified step 5 for a uninstall/reinstall. The CAVEAT about Catalyst rules doesn't apply since you will be importing into essentially the same hostname FMS.
See SOL46240
Export/Import Rules PROCEDURE:
CAVEAT: The Rules export file will contain 'Catalyst' rules which are specific to the original FMS. If one is attempting to import ALL the rules from an exported file into another FMS of a different name, these 'Catalyst' entries should be edited/removed from your final version rules file before importing . Also, the installed cartridges on the target server MUST match the cartridges installed from the source FMS.

1) Access the jmx-console and login with foglight user and password:
http://<your_fms>:<port>/jmx-console/

2) Scroll down to service=import/export and select

3) Search this page for void exportRulesToFile(); enter the Rules filename desired in the ParamValue field & select Invoke.
(this saves the file in %FGLHOME% on the Foglight Management Server (FMS) )

4) Search the same page for void exportRegistryVariablesToFile() - enter the Registry filename desired in the ParamValue field & select Invoke. (file saved in same location as step 3)

5) Move your exported files to a 'safe' directory outside of $FGLHOME and then Uninstall/Reinstall your FMS. Install all the same cartridges as existed previously.

6) Move your exported files to $FGLHOME and Import the registry and/or rules file via the jmx-console | service=import/export |void importFromFile(). Enter the registry or rules filename in the ParamType field and select Invoke.

Feedback inviato

Questo articolo ti è servito per risolvere il problema?

Seleziona valutazione

Request a KB Article

Contenuti consigliati

Prodotto/i:: Foglight
5.5.8, 5.5.5, 5.5.4.1, 5.5.4, 5.5.2, 5.5

Argomento/i:: Troubleshooting

Cronologia articoli:: Data di creazione: 2/24/2011
Ultimo aggiornamento: 5/7/2023

Cerca in tutti gli articoli

Seleziona il prodotto:

Per una maggiore efficacia, compilare l'Obiettivo della chat:

Soluzioni consigliate per il problema

FMS logs "ORA-04098: trigger 'SYS.XDB_PI_TRIG' is invalid and failed re-validation" (4324680)

Titolo

Descrizione

Causa

Risoluzione

Leave a Comment