Maximo部分FAQ

1.ConfigDB发生表空间错误？
答：
有时configdb时出现错误：

ORA-00959: Tablespace 'MAXIMO' does not exist
或者
ORA-02216: Tablespace name expected

1、如果你安装ORACLE后设置的表空间不是“MAXIMO”这个名字，那么

必须在MAXINST时使用-Tname参数。

如果你真的不清楚设置的表空间是什么名字，那么执行下列语句：

UPDATE MAXTABLE SET STORAGEPARTITION = 

(SELECT TABLESPACE_NAME FROM USER_TABLES WHERE TABLE_NAME = TABLENAME);

UPDATE MAXTABLECFG SET STORAGEPARTITION = 

(SELECT TABLESPACE_NAME FROM USER_TABLES WHERE TABLE_NAME = TABLENAME);

COMMIT;

2、如果你有一个名为XXXXXXX的表空间，那么在SQLPLUS中以MAXIMO模式的用户和密码登录：

UPDATE MAXSYSINDEXES SET STORAGEPARTITION = 'XXXXXXX';
COMMIT;

3、修正存储空间字段的域

*进入MAXIMO，转到——配置——域

*找到DBSTORAGEPARTITION域

*为没有列在其中的表空间新增一行。
*删除那些实际上不存储的表空间记录。 
 

2.如何指定记录显示的行数？
答：The setting for the maximm number of rows allowed for select rows on results/list tables

can be found in the webclient.properties file.

（结果集和列表的行数设置可以在webclient.properties找到。）
例如:
C:/MAXIMO/applications/maximo/properties/webclient.properties

 找到如下参数

# the maximum number of rows allowed for select rows on results/list tables.
webclient.maxselectrows=200

将参数设置为200，保存该文件，并rebuild maximo.ear包使其生效。

3.如何增加分类的结点数？
答：MXES分类树状列表有50行的显示限制。

a. 编辑control.jsp文件

c:/maximo/applications/maximo/maximouiweb/webmodule/webclient/controls/tree/control.jsp

b. 更改下列参数到你想要的值:

int CONST_TREE_NODE_CHILDREN_COUNT_DEFAULT = 50;

c. rebuild和重新部署Maximo ear文件

4.如何增加MXMESSAGES？
答：How to Modify or Create Messages in Maximo Enterprise Suite (MXES)

Overview : This document explains how to change Maximo messages or add new ones.

Messages

Messages are all stored in the database under the MAXMESSAGES table.
所有MAXIMO的消息都存储在MAXMESSAGES表中。

Below are two records from the MAXMESSAGES table.
Messages are grouped into applications. There is a unique MSGKEY id for each message value within the MSGGROUP.

There are two different display methods available: MSGBOX and STATUS.

MSGBOX is a popup message box that displays with different types of buttons or icons as options.

STATUS is message displayed on the navbar.

MSGBOX是弹出对话框，可以与用户交互。

STATUS是显示在导航栏上的消息，起提示作用。

• Changing/Adding Messages

The wording on messages can be changed or new messages can be created based upon your preferences.

There are two different methods available to change or add messages.

SQL statements can be created to update or insert records on the MAXMESSAGES table

or changes can be made through an xml file.

可以通过SQL语句在MAXMESSAGES进行INSERT、UPDATE等，也可以修改XML文件。

To create XML file with all messages, download all the records from the MAXMESSAGES table

by running the following command in DOS:

maximo_root /tools/maximo/internal>messageunloader.bat

可以通过上述批处理文件生成messages.xml再进行编辑。
This program will create a messages.xml file located in the tools/maximo/internal folder.

It will use the database connection properties in the applications/maximo/properties/maximo.properties file

to connect to local database.

The default behavior can be overridden using the -f switch to specify a different property file

or the -i switch (-ic:/maximo/resources/messages/ messages.xml) to save the XML file

to resources/messages folder because the messageloader program

makes the assumption the file is located in this directory on upload.

Edit the messages between the value tags.

Below is an extract taken from messages.xml.

<?xml version="1.0" encoding="ISO-8859-1"?>

<messages version="Merlin">

<group id="workorder">

<key id="failurecode">

<display method="MSGBOX">

<option>MSG_BTNOK</option>

</display>

<value>{0} {1} is not a valid failure class.</value>

</key>

<key id="problemcode">

<display method="MSGBOX">

<option>MSG_BTNOK

</display>

<value>{0} {1} is not a valid problem code.

</key>

</group>

</messages>

If new messages need to be created, we recommend a new messages XML file be created.

The extract taken from messages.xml can be used as a base to create your new messages XML file.

The format is the same as messages.xml with the exception of cleanup="false" in the messages tag.

<messages version="Merlin" cleanup="false">

增加上述参数后，可以防止MAXMESSAGES表中已存在消息被删除。
By adding this parameter, it will prevent all existing messages in MAXMESSAGES table from being deleted.

Using the extract as the base, the following tags, group, key id, display method, option,

and value, will need to be replaced with new values.

Group - This value is usually associated to the application name. The group tag contains one or more key tags.
Key - This value is the unique id for the message value.
Display - The display tag must be contained in a key tag. The method property may be MSGBOX or STATUS.
Option - The display tag may contain one or more option tags. Right now, only MSGBOX has options. The options define which buttons are displayed. The following options are available for MSGBOX:

MSG_BTNCLOSE - displays message box with close button; represented in the database as 1
MSG_BTNOK - displays message box with ok button; represented in the database as 2

MSG_BTNCANCEL - displays message box with cancel button; represented in the database as 4

MSG_BTNYES - displays message box with yes button; represented in the database as 8

MSG_BTNNO - displays message box with no button; represented in the database as 16

MSG_ICONWARNING - displays message box with warning icon; represented in the database as 32

MSG_ICONSTOP - displays message box with stop icon; represented in the database as 64

MSG_ICONEXCLAMATION - displays message box with exclamation icon; represented in the database as 128

Value - The key tag must contain one, and only one, value tag. The value tag has no properties.

Save the changes and upload all the records in the XML file back to MAXMESSAGES table by running the following command in DOS:

Using maxmessages.xml:

maximo_root /tools/maximo/internal>messageloader.bat

Using new XML messages file:

maximo_root /tools/maximo/internal>messageloader.bat -ic:/merlin/resources/messages/ newmessages.xml

This program assumes the messages.xml file is located in the resources/messages folder

and uses the database connection properties in the applications/maximo/properties/maximo.properties file

to connect to your local database.

The default behavior can be overridden using the -f switch to specify a different property file

or the -i switch (-ic:/merlin/resources/messages/ newmessages.xml) to use a different xml file.

If the upload process fails, a -d flag can be used and all group/key entries as they are imported will be displayed.

5.如何配置ORACLE TEXT查询？
答：Users cannot find records when querying the Description field. Oracle Text indexes are not being updated.

用户无法通过描述字段查找记录，是因为ORACLE TEXT索引没有被更新导致的。

Overview : Users are complaining that they cannot find records when they query on words in the description.

They can find the records when they query using fields other than Description. This is Oracle only.

总览：用户经常抱怨他们无法通过描述字段来查询记录，但是其他字段就可以，这个现象仅仅发生在ORACLE数据库中。

Maximo Enterprise Suite creates Oracle Text indexes on each table's DESCRIPTION column so that users can quickly

and efficiently search for records containing specific words in the description. When records are created

or updated, Oracle Text indexes are not automatically updated by the database. Instead, a process

must be run to update the indexes for each table. The MXES installation program (MAXINST)

creates a stored procedure named MAXIMO_TS_JOB to perform this update on all tables.

 It also creates a second stored procedure named MAXIMO_TS_JOB_CALL

that submits MAXIMO_TS_JOB as an Oracle batch job to run every five minutes.
mxes 为每张表的描述(description)列创建Text索引，以便用户能够快速和有效地查询数据。

当创建和更新记录时，oracle的text索引不能自动更新。

必须执行一个过程叫maximo_ts_job的过程来更新每张表的text索引.

并且mxes还创建了第二个存储过程，名为maximo_ts_job_call，

用于将maximo_ts_job设置成每5分钟执行一次的job。

Note: If you are running MXES Patch 03 or higher on Oracle 10g, there has been a change to use

DBMS_SCHEDULER instead of DBMS_JOB to control the execution of the index synchronization procedure.

The MXES schema must be given the CREATE JOB privilege in order to use DBMS_SCHEDULE.

This is explained in the MXES Patch 03 Release Notes.

注意：如果你使用mxes patch 03或者oracle 10G以上的数据库，

dbms_scheduler将替换dbms_job来控制index同步过程的执行。用户必须被

授予创建job的权限才能使用dbms_schedule.

If users are complaining that they cannot find records when they query with values in the description field

of an application, check the following:

如果用户抱怨他们无法通过描述字段来查询记录，按以下顺序进行检查。

Ask them to check again after waiting five minutes, or ask them to query using a key value

such as the Asset or Workorder number instead of the description. If the records are found then

the Oracle Text index update is working normally. It takes around five minutes for the Oracle Text indexes

to get updated. Shortening this interval is not advisable as it would increase the load on the database.

 Ask the users to be patient, or to query using key values it they need to go back to a record that they just created.

If the above does not seem to be working, run the following select from SQLPLUS logged in as MAXIMO:

让他们5分钟后再执行查询，或用其他字段进行查询。如果记录能够被查询出来，说明text index更新工作正常。

如果还是不行，
用maximo用户在sqlplus中运行以下脚本。

select object_name from user_objects where object_type = 'PROCEDURE';

OBJECT_NAME
--------------------------------------------------------------------------------
MAXIMO_GATHER_TABLE_STATS
MAXIMO_TS_JOB
MAXIMO_TS_JOB_CALL

(MAXIMO_GATHER_TABLE_STATS is the procedure that is executed to update statistics on tables

and indexes from the Database Configure application.)

maximo_gather_table_stats 是用来更新数据库表和索引的统计信息的。

If you do not see the MAXIMO_TS_JOB procedure, you should run the following script to create it:

CREATE OR REPLACE PROCEDURE maximo_ts_job AS
BEGIN
for idx in (select pnd_index_name iname from ctx_user_pending)
loop
CTX_DDL.SYNC_INDEX(idx.iname);
end loop;
END;
/

If you do not see the MAXIMO_TS_JOB_CALL procedure, you should run one of the following scripts

 to recreate it:

On Oracle 9i:

CREATE OR REPLACE PROCEDURE maximo_ts_job_call AS
JobNo NUMBER;
BEGIN
dbms_job.submit(JobNo, 'begin maximo_ts_job; end;', SYSDATE, 'SYSDATE + 5/1440');
COMMIT;
END;
/

On Oracle 10:

CREATE OR REPLACE PROCEDURE maximo_ts_job_call AS
BEGIN
  dbms_scheduler.create_job(
  job_name => 'MAXIMOTSSYNC',
  job_type => 'STORED_PROCEDURE',
  job_action => 'maximo_ts_job',
  start_date => SYSDATE,
  repeat_interval => 'SYSDATE + 5/1440',
  enabled => TRUE);
END;
/

Run the following to submit the job to run every five minutes (as indicated by the SYSDATE + 5/1440 above):

exec maximo_ts_job_call();
Then test after a five minute wait by creating a new record with a unique value in the description

and searching for it. If it still does not work there may not be any job queues defined.

You can check this by logging in as SYSTEM in SQLPLUS and executing:

select name,value from v$parameter where name = 'job_queue_processes';

If the result is a value of 0, then run the following to create a couple of job queue processes:

alter system set job_queue_processes = 2 scope = both; 如果上述语句出现错误提示，那么把scope = both去掉;

Then connect as MAXIMO again and resubmit the batch job:

exec maximo_ts_job_call();