13 OSM Log Messages

This chapter details the Oracle Communications Order and Service Management (OSM) log messages. The sections included in this chapter are:

• OSM Catalog Messages

• Automation Catalog Messages

OSM Catalog Messages

Table 13-1 shows OSM Catalog messages.

Table 13-1 OSM Catalog Messages

Error Code	Severity	Description
600000	error	Message Body Order type/source is not found. The order type={1} /source={0} either does not exist, or is not available to the user. Message Details The order type={1}/ source={0} either does not exist, or is not available to the user. Method logSourceTypeNotFound(String source, String type)
600001	error	Message Body Order is not found. The order with orderid={0} and orderHistId={1} does not exist, or is not available to the user. Message Details The order with orderid={0} and orderHistId={1} does not exist, or is not available to the user. Cause The orderHistId might not be up to date. Action Refresh server. Method logOrderNotFound(String orderId, String orderHistId)
600002	error	Message Body Order template is not found. The order template does not exist, or is not available to the user. Message Details The order template does not exist, or is not available to the user. Method logOrderTemplateNotFound()
600003	error	Message Body Remark is not found. The given remark (orderid={0}, histid={1} remarkid={2}) does not match a remark in OMS. Message Details The given remark (orderid={0}, histid={1} remarkid={2}) does not match a remark in OMS. Cause Remark might have been deleted from the server or cannot be found in a specified location. Action Contact your local administrator. Method logRemarkNotFound(String orderId, String orderHistId, String remarkId)
600004	error	Message Body Header for mnemonic path is not found. The header for mnemonic path={0} does not exist, or is not available to the user. Message Details The header for mnemonic path={0} does not exist, or is not available to the user. Method logHeaderNotFound(String mnemonicPath)
600005	error	Message Body The format of the order data is not correct. The message details the error location. Invalid data = {0} Message Details Invalid data = {0} Method logOrderDataInvalid(String orderdata)
600006	error	Message Body An attempt to update an order was made without first retrieving the order with an Accept parameter of true. Order (orderid={0} histid={1}) has not been accepted by user={2}. Message Details Order (orderid={0} histid={1}) has not been accepted by user={2} Cause An attempt to update an order was made without accepting the order. Action You should accept the order first, then update the order. Method logOrderNotAcceptedByUser(String orderId, String orderHistId, String userid)
600007	error	Message Body Order update failed. The order (orderid={0} histid={1}) could not be updated due to a data format error. The message details the reason for failure. Data={2} Message Details The order (orderid={0} histid={1}) could not be updated due to a data format error. The message details the reason for failure. Data={2} Cause Data format error. Action Make sure all your data are in correct format and comply with their masks. Method logOrderUpdateFailed(String orderId, String histid, String data)
600008	error	Message Body Mandatory check failed. A mandatory field was not given a value when attempting to create, assign, complete, or suspend an order. {2} number of data was missing for order with order id={0}, order history id={1}. The first missing/extra node is node id={3} and order type={4}. Message Details Mandatory check failed. A mandatory field was not given a value when attempting to create, assign, complete, or suspend an order. {2} number of data was missing for order with order id={0}, order history id={1}. The first missing/extra node is node id={3} and order type={4} Cause Not all mandatory fields are filled. Action Fill in data for all mandatory fields. Method logMandatoryCheckFailed(String orderID, String orderHistID, String num, String firstNodeID, String firstNodeType)
600009	error	Message Body Transition is invalid. The order (orderid={0} histid={1}) cannot be transitioned to state={2}. Use ListStatesNStatuses.Request to get a list of valid states. Message Details The order (orderid={0} histid={1}) cannot be transitioned to state={2}. Use ListStatesNStatuses.Request to get a list of valid states. Cause Cannot transition to the selected state. Action Use the ListStatesNStatuses XML API request to get a list of valid states. See OSM Developer's Guide for information. Method logTransistionInvalid(String orderid, String histid, String state)
600010	error	Message Body Unable to accept order. When retrieving an order for update, the order (orderid={0} histid={1}) cannot be accepted by the current user={2} Message Details When retrieving an order for update, the order (orderid={0} histid={1}) cannot be accepted by the current user={2}. Cause The orderid and histid are not up to date, or the order has been accepted by another user. Action Refresh the server to get new orderid and histid. If the order is currently accepted by another user, you cannot perform Accept operation. Method logUnableToAccept(long orderid, long histid, String userid)
600011	error	Message Body User is not found. The order orderid={0} histid={1} cannot be assigned to userid={2}. Message Details The order orderid={0} histid={1} cannot be assigned to userid={2}. Cause User is not found. Action Try to assign the order to another user. Method logUserNotFound(String orderid, String histid, String userid)
600012	error	Message Body Invalid state mnemonic. The order (orderid={0} histid={1}) cannot be suspended with the given state (state={2}) mnemonic. Note: Only user-defined states are valid. If you want to complete or assign an order, you must use the appropriate request. Message Details The order (orderid={0} histid={1}) cannot be suspended with the given state (state={2}) mnemonic. Note: Only user-defined states are valid. If you want to complete or assign an order, you must use the appropriate request. Cause You are calling suspendOrder with an invalid user defined state. Action Supply a valid user defined state, or try to use other appropriate requests. Method logInvalidStateMnemonic(String orderid, String histid, String state)
600013	error	Message Body Invalid status mnemonic. The order (orderid={0} histid={1}) cannot be completed with the given status mnemonic (status={2}). Message Details The order (orderid={0} histid={1}) cannot be completed with the given status mnemonic (status={2}). Cause The status might not be valid for the current task. Action Supply a valid status. Method logInvalidStatusMnemonic(String orderid, String histid, String status)
600014	error	Message Body Remark cannot be modified. The time interval in which a created remark can be modified has elapsed. The remark can no longer be modified. (orderid={0} histid={1} remarkid={2} userid={3}) Message Details Remark cannot be modified. The time interval in which a created remark can be modified has elapsed. The remark can no longer be modified. (orderid={0} histid={1} remarkid={2} userid={3}) Method logRemarkCannotBeModified(String orderid, String histid, String remarkid, String userid)
600015	error	Message Body Request Unknown. The request type could not be identified. Type given={0} Message Details The request type could not be identified. Type given={0} Method logRequestUnkown(String type)
600016	error	Message Body Request parameter error. A parameter for the request is missing or invalid. The message details the parameter in question Parameter = {0}, request type = {1}. Message Details A parameter for the request is missing or invalid. The message details the parameter in question Parameter = {0}, request type = {1}. Method logRequestParameterError(String parameter, String requestType)
600017	error	Message Body Not authorized. The user={0} is not authorized to make the request={1}. Message Details The user={0} is not authorized to make the request={1}. Cause The user is not authorized to perform the operation. Method logNotAuthorized(String userid, String request)
600018	error	Message Body Database connection failed. Method logDatabaseConnectionFailed()
600019	error	Message Body Security violation by user = {0} Cause User is not authorized to perform this operation. Method logSecurityViolation(String userid)
600020	error	Message Body Naming exception was thrown while looking up JNDI name={0}. Cause JNDI name might not exist. Action Contact your local administrator. Method logNamingException(String name)
600021	error	Message Body Remote exception thrown, while access object = {0} Message Details Remote exception was thrown while working with an EJB. Method logRemoteException(String name)
600022	error	Message Body EJB Create exception thrown while creating object={0}. Message Details EJB Create exception thrown. Method logEJBCreateException(String name)
600023	error	Message Body Unknown exception thrown, message={0}. Message Details Unknown exception thrown, message={0}. Method logUnknownException(String message)
600024	error	Message Body Cannot deliver JMS message to queue = {0} Message Details Cannot deliver JMS message. Cause JMS Queue might be down. Method logCannotDeliverMessage(String arg)
600025	error	Message Body Invalid XML document, doc={0}. Message Details Invalid XML document, doc={0}. Cause XML document has syntax errors. Action Fix the syntax errors. Method logInvalidXMLDocument(String doc)
600028	debug	Message Body SQL: {0} Message Details SQL statement execution Method logSQL(String sql)
600029	debug	Message Body {0} Message Details Log of a request with all its parameters, based on a toString() Method logRequestWithParameters(com.nortel.oms.request.Request request)
600030	debug	Message Body Creating order node: mnemonic path {0}, node id {1}, node type {2}, node index {3}, parent index {4}, double value {5}, value {6}, parent new? {7} Message Details Node information was sent to the database Cause An order node has been created Action None Method logNodeCreate(String mnemonicPath, long nodeID, String nodeType, long nodeIndex, long parentIndex, double doubleValue, String value, String parentNew)
600031	debug	Message Body Deleting Order Node: node ID {0}, node type {1}, node index {2}, old double value {3}, old text value {4} Message Details Node information was sent to the database Cause An order node has been deleted Action None Method logNodeDelete(long nodeID, String nodeTypeCode, long nodeIndex, double oldDoubleValue, String oldValue)
600032		Message Body Updating Order Node: mnemonic path {0}, node ID {1}, node type {2}, node index {3}, old double value {4}, old text value {5}, new double value {6}, new text value {7} Message Details Node information was sent to the database Action None Method logNodeUpdate(String mnemonicPath, long nodeID, String nodeTypeCode, long nodeIndex, double oldDouble, String oldText, double newDouble, String newText)
600035	debug	Message Body Data validation failed in order editor. Node (name={0} nodeid={1} nodetype={2} nodeIndex={3} nodeDataType={4} mask={5}) does not comply with mask. Order ID={6} and user={7} Message Details Node (name={0} nodeid={1} nodetype={2} nodeIndex={3} nodeDataType={4} mask={5}) does not comply with mask. Order ID={6} and user={7} Cause Data supplied do not comply with their masks. Action Must supply data with correct format. Method logOrderEditorDataValidationFailed(String name, String nodeId, String nodeType, String nodeIndex, String nodeDataType, String mask, String orderID, String user)
600036	debug	Message Body Order editor - Create a node. Message Details Order editor: create a node (nodeId={0} nodeType={1} parentWebID={2}) Method logOrderEditorCreateNode(String nodeId, String nodeType, String parentWebID)
600037	debug	Message Body Order editor - delete a node Message Details Order editor - delete a node (webID={0}) Method logOrderEditorDeleteNode(String webID)
600038	debug	Message Body Notification Engine - create message. Message Details Creation of event message Method logNotificationEngineCreateMsg(String arg)
600039	debug	Message Body Could remove an event from the DB. Event Id = {0} Method logEventEngineRemoveEvent(long eventID)
600055	warning	Message Body An exception occurred while removing the session for user {0}. Reason: {1}. Message Details While logging out user {0}, an exception was thrown when calling EJBObject.remove(). Cause The server does not allow the session to be removed, or a communication error occurred. Method logEJBRemoveException(String username, Throwable th)
600063	error	Message Body Error loading screen definitions from {0}. Reason: {1}. Message Details The screen definition file {0} could not be loaded. The screen definition file is required to construct the web pages. Cause The OMS application has not been deployed or built properly. Action Make sure that the screendefinitions.xml file is in the oms.ear file: oms.ear/oms.war/WEB-INF/conf/ Method logCouldNotLoadScreenDefinitions(String url, Throwable th)
600066	warning	Message Body Poller cannot locate listener {0}. Reason: {1}. Message Details Cause Poller Servlet was deployed before listener {0}. Action None Method logGetPollerListener(String listener, Throwable th)
600069	error	Message Body Could not unsubscribe for {0} event. Message Details Event unsubscription for {0} event has failed. Cause JMS queue might be down. Action Use the WebLogic Server Console to verify JMS deployment. Method logEventTypeUnsubscribeException(String eventType)
600071	debug	Message Body Filter value {1} does not have the proper format ({3}) for {0}. Message Details A filter could not be generated using the value {0}, formatter for {1} and mask {3} Cause User error Action Expected. You must retry. Method logFilterFormatError(String headerName, String filterValue, String mask)
600072	debug	Message Body {3} invalid. Wildcards are not permitted for operation {1} for header {0} Message Details {3} invalid. Wildcards are not permitted for operation {1} for header {0} Cause User input. Expected error. Action You must retry. Method logFilterWildcardError(String headerName, String operationType, String value)
600073	error	Message Body SSL is not enabled. Message Details SSL is not enabled. Cause SSL is not enabled. Action You must have SSL enabled for your server through WebLogic console. Method logSSLDisabled()
600076	error	Message Body Unable to connect to remote file system for accessing attachments. Message Details Unable to connect to T3 remote file system for accessing attachments. Cause Targeted server might be down. Action Contact your local administrator. Method logT3ConnectionException()
600077	error	Message Body Unable to add attachment with id={0} in remote file system. Message Details Unable to add attachment with id={0} in remote file system using T3 file services. Cause IO Exception. Method logT3AddAttachmentException(String attachmentID)
600078	error	Message Body Unable to delete attachment with id={0} in remote file system. Attachment with id={0} does not exist. Message Details Unable to delete attachment with id={0} in remote file system using T3 file services. Attachment with id={0} does not exist. Cause The attachment does not exist. Method logT3DeleteAttachmentNotFoundException(String attachmentID)
600079	error	Message Body Unable to read attachment with id={0} in remote file system. Message Details Unable to read attachment with id={0} in remote file system using T3 file services. Method logT3ReadAttachmentException(String attachmentID)
600086		Message Body Retrieve PendingOrdersReport Message Details Retrieve PendingOrdersReport with orderTypesID={0}, orderSourceID={1}, summaryLevel={2} Method logPendingOrdersReport(String orderTypesID, String orderSourceID, String summaryLevel)
600088	error	Message Body Unable to add attachment with id={0} in remote file system. Attachment with id={0} already exists. Message Details Unable to add attachment with id={0} in remote file system using T3 file services. Attachment with id={0} already exists. Cause The attachment already exists. Action None Method logT3AddAttachmentAlreadyExists(String attachmentID)
600089	error	Message Body Unable to add attachment with id={0} in remote file system. Attachment with id={0} exceeds maximum file size specified in the configuration file. Message Details Unable to add attachment with id={0} in remote file system using T3 file services. Attachment with id={0} exceeds maximum file size specified in the configuration file. Cause Your attachment size is too big. Action Increase the size of the max_attachment_size parameter in the oms-config.xml file. See "Configuring OSM with oms-config.xml" for more information about editing the oms-config.xml file. Method logT3AddAttachmentExceedMaxFileSize(String attachmentID)
600090	error	Message Body Unable to read attachment with id={0} in remote file system. Attachment with id={0} does not exist. Message Details Unable to read attachment with id={0} in remote file system using T3 file services. Attachment with id={0} does not exist. Cause The attachment does not exist. Action None Method logT3ReadAttachmentNotFound(String attachmentID)
600091		Message Body SSL port is not found. Message Details SSL port is not found. Cause Either server is not found, or there is no SSL port set up for the current server. Action Make sure SSL port was set up through WebLogic console. Method logSSLPortNotFound()
600092	error	Message Body MBean home is not found. Message Details MBeanHome.ADMIN_JNDI_NAME cannot be found. Cause MBeanHome.ADMIN_JNDI_NAME cannot be found. Action None Method logMBeanHomeDisabled()
600093	error	Message Body DataSource connection to database could not be found. Message Details The EJB requesting a connection to the database does not have a DataSource configured. This caused the data access object to fail. Cause The database could not be located on server startup, or the EJB deployment descriptor ejb-jar.xml is missing a resource-ref to jdbc/DataSource, or WebLogic-ejb-jar.xml is missing a resource-descriptor tag to ordermanager/oms1/internal/jdbc/DataSource Action Determine if the database is available. Determine if EJB has correct deployment descriptor Method logDataSourceNotFound()
600098	error	Message Body The current server name cannot be found Message Details The current server name cannot be found Cause MBean cannot find current run time server Action None Method logserverNameNotFound()
600099	error	Message Body Get max_read_only_field_length property from oms-config.xml has failed. Message Details Get max_read_only_field_length property from oms-config.xml has failed. Cause max_read_only_field_length entry does not exist in oms-config.xml. Action Make sure max_read_only_field_length entry exists in oms-config.xml. Method logGetMaxReadOnlyLengthError()
600103	error	Message Body OMS is not enabled to send {0} event to the automated agent. Cause Either it is disabled in oms-config.xml file or the {1} key is not found in the file. Action Make sure it is {1} key in the oms-config.xml file is set to true. Method logDisabledJMSEvent(String event, String key)
600104	error	Message Body Exception thrown while trying to enable or disable {0} event. Method logExceptionFindListenerForJMSEvent(String event)
600105	warning	Message Body Cannot send messages. JMS connection is down. Cause JMS connection is down. Action Use the WebLogic Server Console to verify JMS deployment. Method logJMSTopicConnectionDown()
600108	error	Message Body An OMS Exception has been thrown. Reason: {0} Method logOMSException(Throwable th)
600109	debug	Message Body Lock successful Message Details Exclusive access to events table granted Method logEventTableLockSuccess()
600110	debug	Message Body Lock failed Message Details Access to events table denied Cause Other instance of Poller servlet holds the lock Action Wait for the current operation to end, and try again. Method logEventTableLockFailure()
600111	error	Message Body Invalid value ({1}) is specified for ({0}) in configuration file. Defaulting to ({2}). Message Details Provided value for a parameter is missing or is invalid. A default value is found in oms-config-defaults.xml file and is defaulted to. Cause Value out of range - nonexisting path - invalid timezone id - incorrect boolean value Action Check max and min values in oms-config-defaults.xml file - correct the path string - find the correct id for your timezone - check how boolean values are represented in oms-conifg-defaults.xml file Method logInvalidValueForParameter(String property, String value, String default)
600112	error	Message Body Invalid value ({1}) is specified for ({0}) in configuration file and no default value found for it in oms-config-defaults.xml file. Message Details Provided value for parameter is missing or is invalid. A default value is not found in oms-config-defaults.xml to default to. Cause oms-config-default.xml file cannot be accessed or it does not provide necessary information for the property in question Action verify oms-config.xml and oms-config-defaults.xml files. check the installation. check the spelling of parameters in oms-config.xml file Method logInvalidValueAndNoDefault(String property, String value)
600114	error	Message Body Error reading configuration parameters XML file(URL: {0}) - {1} - {2} Message Details An error happened while accessing or reading the indicated configuration file. Cause passing error - a malformed URL F119G120E120- G120I/O exception Method logErrorLoadingConfigXMLFile(String url, String cause, String msg)
600115	error	Message Body In class {0}, an SQL Statement was not closed after use. It will now be closed. Cause AbstractProxy.close() was not called after using SQL connection Action Report problem to development Method logStatementNotClosed(String classname)
600116	error	Message Body In class {0}, an SQL Connection was not closed after use. It will now be closed. Cause AbstractProxy.close() was not called after using SQL connection Action Report problem to development Method logConnectionNotClosed(String classname)
600117	warning	Message Body The view node {0} of type {1} has an invalid default value of {2}. The value has been ignored. Cause The default value is not entered correctly, or is incorrect for the data type. Action Change default value. Method logInvalidDefaultOrderNodeValue(String mnemonicPath, String nodeType, String default)
600118	error	Message Body Unable to locate resource bundle. Cause Resource does not exist. Action Make sure there exist a resource file named {0}_ {1}.properties with key(s) {2}. Method logI18NMissingResourceException(String baseName, String locale, String key)
600119	error	Message Body Poller failed in init, message={0}. Method logPollerInitFailure(String msg)
600120	error	Message Body Processing of timeout event failed, message={0}. Method logPollerProcessTimeoutFailed(String msg)
600121	error	Message Body Unexpected system exception processing XML request: {0} Cause Unexpected system exception processing XML request: {0} Action Report to development Method logXMLAPIProcessorError(Throwable th)
600122	debug	Message Body XMLAPI Servlet, message={0}. Method logXMLAPIServletTrace(String msg)
600123	error	Message Body Could not load XMLAPI Servlet request mappings. Servlet will be unavailable. Cause xml-request-mappings.xml file is missing. Action check web application WEB-INF/conf directory. Method logRequestMappingUnavailable(Exception reason)
600127	warning	Message Body Error reading XML Document: {0} Method logErrorReadingXML(Exception cause)
600128	warning	Message Body An error occurred processing XML request: {0} {1} : message {2} Method logXMLApplicationException(int code, String desc, String msg, Exception ex)
600129	warning	Message Body SQL Exception {0} : {1} Method logSQLException(int errorCode, String message, Throwable th)
600132	error	Message Body Unable to add attachment. Attachment exceeds maximum file size={0} specified in the configuration file. Message Details Unable to add attachment. Attachment exceeds maximum file size={0} specified in the configuration file. Method logAddAttachmentExceedMaxFileSize(String maxFileSize)
600133	error	Message Body Invalid oms configuration on attachments. Attachment file system must not be null or empty. Maximum attachment size must be bigger than zero. Message Details Invalid oms configuration on attachments. Attachment file system must not be null or empty. Maximum attachment size must be bigger than zero. Method logInvalidOmsConfigurationOnAttachments()
600134	error	Message Body Missing T3 file service with name={0}. Message Details Missing T3 file service with name={0}. Cause Missing configuration of T3 file server name in WebLogic console. Action Contact your local administrator to set T3 file server. Method logMissingT3FileServiceName(String fileSystemName)
600135		Message Body T3 file service with name={0} must target exactly to one server. Message Details T3 file service with name={0} must target exactly to one server. Cause T3 file service was targeted to more than one server. Action Contact your local administrator to set up T3 file server properly. Method logDuplicateT3FileServiceTarget(String fileSystemName)
600136	error	Message Body Invalid T3 file service path. Message Details Invalid T3 file service path. Cause Invalid T3 file service path. Action Make sure T3 file service path is valid. Method logInvalidT3FileServicePath()
600138	error	Message Body Targeted server = [{0}] for the T3 File Service with name = [{1}] is not running. Message Details Targeted server = [{0}] for the T3 File Service with name = [{1}] is not running. Cause Targeted server = [{0}] for the T3 File Service with name = [{1}] is not running. Action Make sure the targeted server is running. Method logTargetedserverForT3FileServiceNotRunning(String t3TargetserverName, String fileSystemName)
600139	debug	Message Body{0}

Automation Catalog Messages

Table 13-2 shows Automation Catalog messages.

Table 13-2 Automation Catalog Messages

Error Code	Severity	Description
700002	debug	Message Body parseXmlData(String xmlData) Method Parse the XML data {0}
700004	debug	Message Body lookupOMSBean(String jndiName) Method Lookup the OMSSession Bean with jndiName={0}
700007	debug	Message Body receiveTask(long orderId, long orderHistoryId, String taskMnemonic) Method Receive Task with orderId={0} orderHistoryId={1} and task mnemonic={2}
700008	debug	Message Body completeTaskOnExit(long orderId, long orderHistId, String taskMnemonic,String comepletStat) Method Complete task On Exit with orderId={0}, orderHistoryId={1}, taskMnemonic={2} and Completion Status={3}
700009	debug	Message Body assignTask(long orderId,long orderHistoryId, String taskMnemonic, String userId) Method Assign Task to {3} with orderId={0} orderHistId ={1} and TaskMnemonic ={2}
700010	debug	Message Body suspendTask(long orderId,long orderHistoryId, String taskMnemonic, String suspendState) Method SuspendTask to state={3} with OrderID={0}, OrderHistId={1} and Task Mnemonic={2}
700011	debug	Message Body acceptTask(long orderId, long orderHistoryId, String taskMnemonic) Method Accept Task with OrderId={0} orderHistryId={1} and taskMnemonic={2}
700012	debug	Message Body updateOrderData1(long orderId,long orderHistId,String TaskMnem, String updateData) Method UpdateOrderData with orderId={0} orderHistoryId={1}, TaskMnemonic={2} and XML Data={3}
700014	debug	Message Body The orderData id={0} and Data:{1} Method printOrderDataAsXML(long OrderId, String OrderData)
700016	debug	Message Body Lookup the Automator: type={0} and jndiName={1} Method lookupAutomator(String type, String jndiName)
700019	debug	Message Body Get a JMS Message with EventType={0}, Mnemonic={1} Method getAMessage(String type, String mnemonic)
700020	debug	Message Body Set the outMessage Correlation to={0} the correlationId={1} Method setCorrelationId(String correlation, String correlationId)
700021	debug	Message Body Send Notification Email message to :{0}, subject:{1}, MessageBody{2} Method sendEmailNotification(String to, String subject, String msgBody)
700023	error	Message Body An automation exception has occurred At {0}, the reason is :{1} Cause See message body. Method AutomationException(String msg, Throwable th)
700024	error	Message Body Naming Exception has occurred at {0} reason {1} Cause Cannot find user plug-in from JNDI tree. Method namingException(String name, Throwable ex)
700033	error	Message Body {0} {1} Cause See message body for details. Method logAutomationException(String desc, Throwable exception)