Servers >>Recall

	Why are no Recall 5.0 projects listed under my data store?
	How do I map a custom field?
	How do I rebuild the Recall data dictionary?

Why are no Recall 5.0 projects listed under my data store

Review the Recall5 data server log file.  If the following line is contained in the log file, then follow the recommendations below.

‘Devkit version incompatible with RECALL installation ‘

Recommendations

1. Check that the version.rdd file is in the $RECALL_HOME/usr/datadict directory.
2. Check that the retcsp file has been edited properly.
3. Check that there are no ^M characters in ANY of the files referenced in the README.  If there are ^M’s then run dos2unix on the files.

Back to Top ...

How do I map a custom field?

In some cases, customers may not populate the WELL.NAME field with valuable information.  Since the WELL.NAME field defines the Identifier and IdentifierType entities for OpenSpirit, then you must figure out what the best definition should be.  For example, one client populates a custom field called WELL.UWI with unique well identifiers.  In order to remap the Identifier and IdentifierType entities for the OpenSpirit Recall data server, you need to edit the openspirit.rdd file under the WELL table and WELLBORE table.  Below are two examples showing the original and edited fields.  Note that the changes need to be made in both the WELL table and WELLBORE table definitions.

Identifier=(ENTITY=WELL,KEY=NAME,TYPE=TEXT)
IdentifierType=(DEFAULT=WELL NAME)

changed to:

Identifier=(ENTITY=WELL,KEY=UWI,TYPE=TEXT)
IdentifierType=(DEFAULT=WELL UWI)

The data dictionary must be rebuilt after these edits are completed in the $RECALL_HOME/etc/datadict_osp/openspirit.rdd file.

Another note is that if you have customized your Recall by creating new Primary Keys, you have to identify those as keys in OpenSpirit's mapping.  For instance, if you have added the OPERATOR column to the Primary Key (or Natural Key) in the Well table, then we must change the status of the OPERATOR column from ‘ATTRIBUTE’ to ‘KEY’, so the resultant lines would change from this:
CurrentOperator=(ENTITY=WELL,ATTRIUTE=OPERATOR,TYPE=TEXT)
to this:
CurrentOperator=(ENTITY=WELL,KEY=OPERATOR,TYPE=TEXT)

Back to Top ...

How do I rebuild the Recall data dictionary?

The Recall Admin should be able to do this for you, but if you need to do it yourself, follow these steps.

UNIX%> su – recall          - become a (the) Recall Admin
UNIX%> cd ~                      - go to the Recall Admin home directory
UNIX%> source .profile   - source the dot profile file to set your environment correctly.

Note: if you have multiple Recall installations, make sure to source the right .profile file.  Some Recall installations combine the .profile into a single file supporting multiple Recall/different version installations.

UNIX%> mk         - run the ‘make’ command to rebuild the data dictionary
Optionally… 
UNIX%> mk DAT - At some client sites you might add the DAT variable to      the make command.  Contact support@petris.com for information.

Note: For this step you must be in the $RECALL_HOME/etc/datadict directory of the correct Recall installation.

Ensure that the data dictionary rebuild was successful by reviewing any output in the console window and by reviewing the $RECALL_HOME/tmp/datadict/datadict.err and datadict.lis files.  Contact support@petris.com for help understanding these files.

Back to Top ...

Site Map   •   Legal   •   Privacy