Setting Threshold Alert For Tablespace Full Free Space (MB) in Enterprise Manager 12c Cloud Control Fails with SQL Error Failed to commit: ORA-13900: missing or invalid parameter warning value

(Doc ID 1391965.1)

Last updated on NOVEMBER 30, 2015

Applies to:

Enterprise Manager for Oracle Database - Version 11.1.0.1 to 12.1.0.2.0 [Release 11.1 to 12.1]
Information in this document applies to any platform.

Symptoms

The error "Failed to commit: ORA-13900: missing or invalid parameter warning value" is returned in Enterprise Manager Cloud Control 12c, when setting the Tablespace Full Metric Thresholds for the Free Space (MB) metric, if the threshold being set is over 1,000.

For example:-

1. In Enterprise Manager 12c Cloud Control, click on targets/databases
2. Choose the particular database
3. On the database home page, underneath the database name, there are 5 choices, "Oracle Database", "Performance", "Availability", "Schema" and "Administration".
4. Click on the drop down menu next to "Administration" and choose "Storage/Tablespaces"
5. Select one of the tablespaces - eg. "Users" and click on "Edit"
6. Click on the "Thresholds" tab
7. Under Free Space (MB) click on "specify thresholds"
8. Enter the value '1024' for Warning (MB)
9. Click on "apply", you get:
SQL Error
Failed to commit: ORA-13900: missing or invalid parameter warning value
The TextBox on the resulting screen now inserts a 'thousands-delimiter' (comma) when 'Apply is clicked', resulting in the above error.
10. Clicking the 'Show SQL' Button displays:

SQL> Begin DBMS_SERVER_ALERT.SET_THRESHOLD(9001,3,'2,048',3,'512',1,1,NULL,5,'tableSpaceName'); END;


11. If you execute the SQL directly on the server, you will receive the same error, but it will succeed if you remove the comma from the '2,048' value above.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms