ARS0015E - Revision history

Jderrick: Substantial additions regarding ARS0015E errors and ars.dbfs - including the situation where a CMOD database is remote.

2022-02-24T21:36:05Z

Substantial additions regarding ARS0015E errors and ars.dbfs - including the situation where a CMOD database is remote.

← Older revision		Revision as of 21:36, 24 February 2022
Line 13:		Line 13:

	Possibly installing a new Content Manager OnDemand server, or probably loading data into CMOD using [[arsload]].		Possibly installing a new Content Manager OnDemand server, or probably loading data into CMOD using [[arsload]].

			If your database instance is remote (i.e. connection to the database is over a network link) there is an error on the database server that either stops CMOD from communicating with the database, or manipulating database tables (create / insert / delete / drop).

	== What happened? ==		== What happened? ==

	~~Either~~ you ~~forgot~~ to put a list of filesystems into the [[ars.dbfs]] file, or all the filesystems listed in ~~that file~~ are full.		If this is a new install, you may have forgotten to put a list of filesystems into the [[ars.dbfs]] file.

			If this is an existing system, either all the filesystems listed in [[ars.dbfs]] are full, or you have a CMOD configuration error or database error.

			If you can't find messages in the System Log, the related tablespace may be offline, and you can get more information by checking the operating system console messages, or [[arslog]].

	== Troubleshooting ==		== Troubleshooting ==
Line 22:		Line 28:
	Check your CMOD configuration. It's likely the problem is one of the items below:		Check your CMOD configuration. It's likely the problem is one of the items below:

			* CMOD is misconfigured - make sure your [[ars.dbfs]] file is configured properly.
	* Your database filesystem is out of space. Expand an existing filesystem with your operating system's tools, or add a new filesystem, and add the name of that filesystem to [[ars.dbfs]].		* Your database filesystem is out of space. Expand an existing filesystem with your operating system's tools, or add a new filesystem, and add the name of that filesystem to [[ars.dbfs]].
	* You don't have access to write to the database filesystem (you must have "rwx" access to read, write, and traverse directories.		* You don't have access to write to the database filesystem (you must have "rwx" access to read, write, and traverse directories.
	* The filesystem where your database stores files may not be available or is not mounted.		* The filesystem where your database stores files may not be available or is not mounted.
	* There are no filesystems listed in the ars.dbfs configuration file, or they have been removed.		* There are no filesystems listed in the ars.dbfs configuration file, or they have been removed.
			* Your database is remote (accessed over a network connection) and that connection has been interrupted, or there is a problem on the database server. Work with your DBA team to investigate further.

	If you cannot add more space to an existing database filesystem, then you can add a new one to the ars.dbfs configuration file (or in the OnDemand Configurator on Windows). You must restart CMOD to load the new configuration information.		If you cannot add more space to an existing database filesystem, then you can add a new one to the ars.dbfs configuration file (or in the OnDemand Configurator on Windows). You must restart CMOD to load the new configuration information.

Jderrick: Minor updates and formatting changes to ARS0015E.

2020-09-25T18:00:29Z

Minor updates and formatting changes to ARS0015E.

← Older revision		Revision as of 18:00, 25 September 2020
Line 16:		Line 16:
	== What happened? ==		== What happened? ==

	Either you forgot to put a list of filesystems into the [[ars.dbfs]] file, or all the filesystems in that file are full.		Either you forgot to put a list of filesystems into the [[ars.dbfs]] file, or all the filesystems listed in that file are full.

	== Troubleshooting ==		== Troubleshooting ==


	Check your CMOD configuration. It's likely the problem is one of the items below:		Check your CMOD configuration. It's likely the problem is one of the items below:
Line 28:		Line 27:
	* There are no filesystems listed in the ars.dbfs configuration file, or they have been removed.		* There are no filesystems listed in the ars.dbfs configuration file, or they have been removed.

	If you cannot add more space to an existing database filesystem, then you can add a new one to the ars.dbfs configuration file (or in the OnDemand Configurator on Windows).		If you cannot add more space to an existing database filesystem, then you can add a new one to the ars.dbfs configuration file (or in the OnDemand Configurator on Windows). You must restart CMOD to load the new configuration information.

Jderrick: Updated error severity text

2015-05-10T01:51:42Z

Updated error severity text

← Older revision		Revision as of 01:51, 10 May 2015
Line 3:		Line 3:
	Message Number: 15		Message Number: 15

	Message Severity: Error		Message Severity: Error (Corrective action is required to continue)

	Message Name: ARS0015E		Message Name: ARS0015E

Jderrick: Standardized the layout.

2015-04-29T00:43:06Z

Standardized the layout.

← Older revision		Revision as of 00:43, 29 April 2015
Line 1:		Line 1:
	Message Text: ~~'''~~Unable to find SMS tablespace filesystems. Either the defined SMS filesystems are full or there are no SMS filesystems defined.~~'''~~		{{TOCright}}
			== What was the error? ==
			Message Number: 15

			Message Severity: Error

			Message Name: ARS0015E

			Message Text:
			Unable to find SMS tablespace filesystems. Either the defined SMS filesystems are full or there are no SMS filesystems defined.

			== What were you doing? ==

			Possibly installing a new Content Manager OnDemand server, or probably loading data into CMOD using [[arsload]].

			== What happened? ==

			Either you forgot to put a list of filesystems into the [[ars.dbfs]] file, or all the filesystems in that file are full.

			== Troubleshooting ==


	Check your CMOD configuration. It's likely the problem is one of the items below:		Check your CMOD configuration. It's likely the problem is one of the items below:

	* Your database filesystem is out of space.		* Your database filesystem is out of space. Expand an existing filesystem with your operating system's tools, or add a new filesystem, and add the name of that filesystem to [[ars.dbfs]].
	* You don't have access to write to the database filesystem (you must have "rwx" access to read, write, and traverse directories ~~('execute')~~.		* You don't have access to write to the database filesystem (you must have "rwx" access to read, write, and traverse directories.
	* The filesystem where your database stores files may not be available or is not mounted.		* The filesystem where your database stores files may not be available or is not mounted.
	* There are no filesystems listed in the ars.dbfs configuration file, or they have been removed.		* There are no filesystems listed in the ars.dbfs configuration file, or they have been removed.

	If you cannot add more space to an existing database filesystem, then you can add a new one to the ars.dbfs configuration file (or in the OnDemand Configurator on Windows).		If you cannot add more space to an existing database filesystem, then you can add a new one to the ars.dbfs configuration file (or in the OnDemand Configurator on Windows).

Jderrick: bolded

2014-10-26T01:32:57Z

bolded

← Older revision		Revision as of 01:32, 26 October 2014
Line 1:		Line 1:
	Message Text: Unable to find SMS tablespace filesystems. Either the defined SMS filesystems are full or there are		Message Text: '''Unable to find SMS tablespace filesystems. Either the defined SMS filesystems are full or there are no SMS filesystems defined.'''
	no SMS filesystems defined.

	Check your CMOD configuration. It's likely the problem is one of the items below:		Check your CMOD configuration. It's likely the problem is one of the items below:

Jderrick: Initial edit

2014-10-26T01:32:26Z

Initial edit

New page

Message Text: Unable to find SMS tablespace filesystems. Either the defined SMS filesystems are full or there are
no SMS filesystems defined.

Check your CMOD configuration. It's likely the problem is one of the items below:

* Your database filesystem is out of space.
* You don't have access to write to the database filesystem (you must have "rwx" access to read, write, and traverse directories ('execute').
* The filesystem where your database stores files may not be available or is not mounted.
* There are no filesystems listed in the ars.dbfs configuration file, or they have been removed.

If you cannot add more space to an existing database filesystem, then you can add a new one to the ars.dbfs configuration file (or in the OnDemand Configurator on Windows).