| Oracle® Fusion Middleware System Administrator's Guide for Content Server 11g Release 1 (11.1.1) E10792-01 |
|
 Previous |
 Next |
Home > System Administrator' > Managing System Migration a... > Troubleshooting Archiving I...
| Oracle® Fusion Middleware System Administrator's Guide for Content Server 11g Release 1 (11.1.1) E10792-01 |
|
Previous |
Next |
Home > System Administrator' > Managing System Migration a... > Troubleshooting Archiving I...
This section provides solutions to several common archiving issues.
This section covers the following topics:
Symptom
I am receiving errors on the importing machine indicating that there are transfer and file extension problems with the documents.
Problem
The following errors were issued to the Archiver log:
Error: Event generated by user <user_name> at host <host_name>. File I/O error. Saving to file collection.hda. Write error. Error: Import error for archive <archive_name> in collection <collection_name>: Content item <item_name> was not successfully checked in. The primary and alternate files must have different extensions.
Recommendation
The I/O error on the export side probably corrupted the batch file and is, in turn, causing the file extension error on the import side. Possible solutions include:
Open the batch file in a text editor and check for invalid data. Try deleting the exported collection.hda file and manually re-run the export/import function.
On the exporting server, open the applicable collection.hda file and look for the lines associated with the content items that caused the file extension error. Some of the revisions of these content items may have the native file in the vault location listed in the alternate file location. There might also be a format entry for the alternate file. Delete these lines and re-import the files.
Add an alternate extensions configuration setting to the Content Server's configuration config.cfg file (IntradocDir/config/config.cfg) on the importing server:
Open the config.cfg file in a text editor:
IntradocDir/config/config.cfg
Locate the General Option Variables section
Enter the following configuration setting:
AllowSamePrimaryAlternateExtensions=true
This configuration setting allows checked in content items to use identical document extensions for both the alternate and primary files.
Save and close the config.cfg file.
|
Note: Although it probably is not necessary to add this configuration setting to the content server config.cfg file on the exporting server, it may be worthwhile to do so for general preventative measures. |
Restart the Content Server.
Question
How can I select and re-run specific batch files from the General tab of the Archiver utility without deleting the remaining files that are required for backup purposes?
Recommendation
The most efficient method would be to create a new collection, copy the desired archives to the new collection, and run the import from there.
Symptom
I configured a value map to change metadata values during the import on an archive collection. But after the transfer, the import maps do not work.
Problem
The metadata values didn't reflect the configured metadata value changes.
Recommendation
To ensure that metadata value changes are retained when the files are exported into an archive and then later imported from that archive, the value maps must be configured on both sides of the transfer process. This means that the same value map must be configured on both the source (exporting) server as well as the target (importing) server.
Question
Due to a system crash, I need to import content from the old archive into a new archive without changing the content information (metadata) of the documents. How can I preface each content item using a letter or number to indicate that all the documents with this designation are new imports (but actually originated from the old archive)?
Recommendation
The archived documents can be re-imported and appropriately marked to distinguish them from other imported content items by applying an import map using the Content ID metadata field. An import map allows you to configure how values are copied from one metadata field to another during import. To set up the import mapm, complete the following steps:
On the Import Maps tab of the Archiver utility, click Edit in the Field Maps section.
The Edit Value Maps screen is displayed.
Select the All check box (leave the Input Value field blank).
Select Content ID from the Field list.
Enter X<$dDocName$> in the Output Value field.
Where 'X' is the letter or number used to distinguish the re-imported content items and 'dDocName' is the database table field value for the document Content ID.
Click OK.
After you re-import the archive, the letter or number used for 'X' should be added to the content ID of each content item. Be sure to configure the same value map on both the source (exporting) server and the target (importing) server. This ensures that the metadata value changes are retained when the files are imported from the archive.
Symptom
When I try to check in or import a content item, the following error message is issued:
Content item already exists.
Recommendation
This error is issued when archiving is done between contribution servers that are using the same autonumbering scheme for content IDs. For example:
'Content ID 003' is checked into content server A and later archived to content server B. If a file is checked into content server B and the next autogenerated number happens to be 003, the error occurs.
'Content ID 005' is checked into both content server A and content server B. If this same content item is archived from content server A to content server B, the error occurs.
Possible solutions include:
Set up an import value map that will add a prefix to the content ID of the imported files. For details refer to "Identifying Imported Content Items From Archive".
In each content server, use the System Properties utility to set up an automatic numbering prefix for checked-in content items:
Start the System Properties utility.
Open the Options tab.
Select the Automatically assign a Content ID on check in check box.
Enter the desired prefix in the Auto Name Prefix field.
Click OK.
Restart the Content Server.
Symptom
I am trying to import content from an exported archive to my proxied Content Server, but the import fails.
Recommendation
For more information about Archiver problems, open and view the Archiver logs (accessible from the content server's Administration page). These logs provide the type of message along with more descriptive information about the logged messages.
For example, if the Archiver log indicates that an import problem involves a metadata field option value that is unavailable, information about configured option lists for metadata fields can be found on the Information Fields tab of the Configuration Manager utility (accessible from the Administration page).
Using this information, compare the option list for the problem metadata field on both the exporting and importing servers. If there are any differences, corrections in one of the servers will make both option lists identical. This would resolve the unavailable option discrepancy.
Symptom
When I run the import function, no errors are issued, but not all of the documents are being imported.
Problem
I exported 428 documents from the development server along with the configuration information (the metadata fields). Then, I transferred the archive to the main production server and ran the import. No errors were issued, so I thought everything had gone well. Unfortunately, when I searched the documents, I discovered that only 198 of the original 428 were actually imported.
Recommendation
Suggestions to resolve this problem include:
Make sure that all Microsoft Word documents are included in the search index.
Particular versions of the search component do not include Microsoft Word documents with embedded links in the search index. Thus, these files will not be found in search queries.
You can remove all embedded links from the affected documents or add the following configuration setting to IntradocDir/config/config.cfg:
CheckMkvdkDocCount=true
This configuration setting ensures that all Word files are included in the search index. However, only the metadata is included, not the full text.
Try exporting the original set of documents and ensure that the source files are deleted. Then re-import the archive that was just exported.
Symptom
My imports are failing.
Problem
The system issues error messages indicating that there are invalid choice list values. I am currently using an option list in the Dependent Choice List applet to configure and control the values.
Recommendation
Apparently a specific metadata taxonomy has been established for your option lists such that there are probably fields that are dependent on each other. In this case, certain values in option lists are available based on what values have been selected in a previous option list. Unfortunately, when using the Archiver, the dependencies in your option lists are obviously conflicting with the content server's capacity to work with custom metadata fields.
A workaround for the conflict involves using the content server's Configuration Manager utility rather than the Dependent Choice List applet. This necessitates that you enter the metadata fields and corresponding option list values on the Information Fields tab of Configuration Manager:
Log into the Content Server as an administrator.
Go to the Administration page and click the Configuration Manager link.
The Configuration Manager utility is started.
Open the Information Fields tab.
Click the Add button and enter one of your metadata field names in the Add Custom Info Field dialog.
Click OK.
The Add Custom Info Field window is displayed.
Complete the fields as appropriate.
In the Option List Type field, choose the Select List Not Validated option.
This option ensures that content whose specified value does not match one currently entered in the Use Option List are nevertheless checked in with the specified value. The Use Option List field lists the name for the list of values a user may choose from for the specified field.
Click OK.
Click the Update Database Design button.
Click the Rebuild Search Index button.
Use this method for the duration of your import process.
Symptom
I used the Archiver to export documents. Now, I'm trying to import them and the process fails.
Problem
When I try to import the previously exported documents, the Content Server issues an error indicating that the 'Company' metadata file is required.
Recommendation
You will need to use the content server's Configuration Manager utility to edit the 'Company' field and make it a non-required field:
Log into the Content Server as an administrator.
Go to the Administration page and click the Configuration Manager link.
The Configuration Manager utility is started.
Open the Information Fields tab.
Select the Company metadata field from the Field Info list.
Click Edit.
The Edit Custom Info Field window is displayed.
Deselect the Require Value check box.
Click OK.
Click the Update Database Design button.
Click the Rebuild Search Index button.
You should now be able to successfully re-import the archive.
Symptom
Some of our product names have changed and we need to update one of the metadata fields in the affected documents. After exporting all the documents with the old product name metadata field, I then attempt to import the documents using the new product name metadata field. But, every time I try this, the Archiver processes only a portion of the total archiving task and then stops.
Problem
Once the Archiver freezes, I am unable to navigate the Content Server user interface and I must shut down all of the open browsers. Also, during the next five minutes after shutting down the browsers, I have no connectivity to the Content Server at all. After this five-minute interval, I can access the Content Server again.
In addition to this freezing problem, the following error message is issued:
Stream error (299) - SKIPPING
Recommendation
One or more processes seem to be interrupting the import. Some possible problem solutions could be any of the following:
The product name metadata field may not have been properly updated in Configuration Manager. Depending on the type of metadata field that the 'product name' is, changing the value could be the reason for the lock-up problem. Is the product name metadata field a (long) text field only or also an option list? If it is an option list, make sure that the new name value is a selection on the corresponding list.
Log into the Content Server as an administrator.
Go to the Administration page and click the Configuration Manager link.
The Configuration Manager utility is started.
Open the Information Fields tab.
Select the product name metadata field from the Field Info list.
Click Edit.
The Edit Custom Info Field window is displayed.
If the Field Type value is Text or Long Text AND the Enable Option List check box is disabled, click OK or Cancel (this should not cause the lock-up problem).
Otherwise,
If the Enable Option List check box is selected, then make sure that the new product name metadata field value is included as a selection on the corresponding list:
Locate the Use Option List field and click Edit.
Enter the new product name metadata field value in the Option List dialog.
Click OK.
Click OK again (on the Edit Custom Info Field window).
Click the Update Database Design button.
Click the Rebuild Search Index button.
The lock-up problem may be due to the indexer's automatic update cycle. The error message indicates that the indexer is failing because it loses connectivity. Every five minutes, the indexer executes an automatic update cycle and could somehow be grabbing the index file and locking it. If so, it might be useful to disable the indexer's automatic update cycle while you run the import.
Log into the Content Server as an administrator.
Go to the Administration page and click the Repository Manager link.
The Repository Manager utility is started.
Open the Indexer tab.
Click the Configure button in the Automatic Update Cycle section.
The Automatic Update Cycle dialog displays.
Deselect the Indexer Auto Updates check box.
Click OK.
|
Note: Be sure to reactivate the automatic update cycle after completing the import. Otherwise, the server will no longer automatically update the index database, which could adversely impact future search results. |
This section covers the following topics:
Question
If I do not create an export query to define the content items to export, will the entire contents of my Content Server be exported?
Recommendation
Yes, test exports have confirmed that leaving the Export Query section blank (not defining an export query) will ensure that the Content Server contents are completely exported.
Question
If I check some documents into the Content Server after I have initiated a large export (but before it completes), will these documents be included in the export? Or, does the Archiver read the timestamp information and determine that the new files are more recent than those originally allocated for the export and not include them? Also, what happens to the archive export if the connection between the servers is interrupted or lost during the export?
Recommendation
When the export is initiated, Archiver runs a query on the system to build a list of the documents that are to be exported. This information is cached and used to build the export archive. Therefore, any new documents that are checked in during the export process will not be included even if they match the export query definition.
If the connection between servers is disrupted, the export process on the source server continues but the transfer to the target server stops. The source server accumulates a number of batch files. While waiting to transfer these files, the source server continues to ping the target server for a connection at regular interval. When the connection is reestablished, the accumulated batch files are transferred to the target server.
If you have used an automated (replicated) transfer, the batch files and their associated content files are removed from the source Content Server. If you have used a manual transfer, the batch files and their associated content files remain in the source Content Server.
Question
How can I export users in an archive?
Recommendation
You can export a users.hda file, which contains the user attributes from the Users database table, as follows:
Log into the content server as an administrator.
Go to the Administration page and click the Archiver link.
The Archiver utility is started.
Open the Export Data tab.
Click Edit in the Additional Data section.
The Edit Additional Data dialog is displayed.
Select the Export User Configuration Information check box.
Click OK.
Symptom
I use the folder archive export feature to move my website hierarchy created by Site Studio. Initially, I can export folders by using the Virtual Folder Administration Configuration page without any problem. However, as my Web site grows, this function does not work anymore. The following errors are issued during the export procedure:
Error <timestamp> Event generated by user '<user>' at host '<host_name>'. Referred to by http://<host>/intradoc-cgi/nph-idc_cgi.exe?IdcService= COLLECTION_GET_ADMIN_CONFIG. Unable to retrieve content. Unable to execute service method 'loadCollectionArchive'. (System Error: Unknown error.) Error <timestamp> IdcAdmin: Event generated by user '<user>' at host '<host>'. Unable to obtain the console output. Unable to execute the service 'GET_SERVER_OUTPUT' on Content Server 'contribution'. Unable to receive request. Response from host has been interrupted. Read timed out.
There is also an out-of-memory error in the Content Server output console:
<timestamp> SystemDatabase#Thread-13: SELECT * FROM Collections, ColMeta WHERE Collections.dCollectionID=ColMeta.dCollectionID AND dParentCollectionID=564 java.lang.OutOfMemoryError Reporting error on thread Thread-13 occurring at <timestamp>. java.lang.OutOfMemoryError java.lang.OutOfMemoryError
Problem
Depending on the size of the folder hierarchy that is being exported as an archive file, the default heap size value for the Java Virtual Machine (JVM) may not be adequate.
Recommendation
In the Content Server's DomainHome/ucm/cs/bin/intradoc.cfg file, comment out the JvmCommandLine setting and increase heap size to 512 M:
#JvmCommandLine=/home/contribution/shared/os/<os>/j2sdk1.4.1/bin/java -cp $CLASSPATH $STARTUPCLASS
JAVA_OPTIONS= -Xmx512m
After restarting Content Server, the archive export function should work correctly again.
This section covers the following topics:
Symptom
The automated transfer function stopped when the target server locked up.
Problem
After restarting the target server, the log file listed an error message stating that there was a problem with a security group and that this prevented the import on the target server.
Recommendation
In this case, obviously the security group problem on the target server must be corrected before the transfer can proceed. Two additional procedures to perform that can help include:
Verifying and testing the outgoing provider ensures that it is set up and working properly:
Log into the source content server as an administrator.
Go to the Administration page and click the Providers link.
The Providers page is displayed.
Click the Info link of the appropriate outgoing provider.
The Outgoing Provider Information page is displayed.
Verify the information.
Return to the Providers page and click the Test link corresponding to the outgoing provider.
In some cases, after problems have been corrected on either the source or the target server, the source server may stop transferring or possibly the automation function no longer works. In either case, restarting Content Server should resolve the problem.
Question
I accidentally started transferring an excessively large file to the production content server. What is the most efficient way to stop the transfer process while it is running?
Recommendation
There are several methods to abort or delete a transfer, including:
The fastest method to abort a running transfer is to disable the source server's outgoing provider:
Log into the source content server as an administrator.
Go to the Administration page and click the Providers link.
The Providers page is displayed.
Click the Info link of the appropriate outgoing provider.
The Outgoing Provider Information page is displayed.
Click the Disable button.
To delete a transfer from the Transfer To tab, complete the following steps:
Log into the source content server as an administrator.
Go to the Administration page and click the Archiver link.
The Archiver utility is started.
Select Options and then Open Archive Collection.
Select the applicable collection from the list.
Click Open.
On the Archiver window, select the source archive in the Current Archives list.
Open the Transfer To tab.
Click Remove in the Transfer Destination section.
You are prompted to confirm the action.
Click Yes.
To delete an automated transfer from the Automation for Instance screen, complete the following steps:
Log into the source content server as an administrator.
Go to the Administration page and click the Archiver link.
The Archiver utility is started.
Select Options and then View Automation For Instance.
The Automation For Instance window is displayed.
Open the Transfers tab.
Select the automated transfer to delete.
Click Remove.
The automated transfer is removed from the list.
Question
What is the best approach to verify the integrity of the files that have been transferred between two servers? Obviously, the documents in the target content server instance should be identical to those in the source instance. I need to ensure that all documents were in fact transferred and if some were not transferred, I must determine which ones failed to transfer.
Recommendation
To ensure that the transferred documents are identical to those on the source server, two items can easily be checked.
The Revisions table:
Specifically, match the contents of the dDocName and dRevLabel columns on both instances and verify the accuracy or discrepancies between them.
The file system:
Check the native file repository:
(DomainHome/ucm/cs/vault/content_type)
and Web-viewable file repository:
(DomainHome/ucm/cs/weblayout/groups/public/documents/content_type)
on each server and verify the accuracy or discrepancies between them.
Symptom
The transfer process is not setting up properly.
Recommendation
If the transfer process is not functioning correctly, check the outgoing provider on the source server and ensure that the information is correct. In particular, make sure that the server host name is correct and matches the HTTP server address.
To verify the server host name on the source server, complete the following steps:
Start the System Properties utility.
Open the Internet tab.
Note the HTTP server address setting.
Go to the Administration page and click the Providers link.
The Providers page is displayed.
Click the Info link of the appropriate outgoing provider.
The Outgoing Provider Information page is displayed.
Check the server host name and make sure it corresponds exactly to the HTTP server address setting in System Properties.
If the server host name setting is different than the HTTP server address, click the Edit button.
Modify the Server Host Name setting as necessary.
Click Update.
Restart the content server.
This section covers the following topics:
Symptom
I am using both WebDav and the content server to check in documents. I would like to be able to view all of the checked-in documents through the WebDAV interface but I can see only the documents that were physically checked in through WebDAV. Currently, I am using the Archiver utility to import the files and have configured a value map using the xCollectionID field. This field is currently set to zero or null and I'm trying to update the value to 182.
Problem
For each file that I try to import, the following error is logged in the Archiver log:
Unable to load collection mappings, too many items.
Recommendation
The error message indicates that you are exceeding the maximum number of items per folder. There is a configurable limit to how many items a folder can hold. To check and update your current limit settings, complete the following steps:
Log into the source content server as an administrator.
Go to the Administration page and click the Folder Configuration link.
The Virtual Folder Administration Configuration page is displayed.
Check the following two limit settings:
Maximum Folders Per Virtual Folder
Maximum Content Per Virtual Folder
Increase both of these limit settings to accommodate your import requirements.
or,
Implement an 'infinite' limit setting by removing the limit setting.
Click Update.
Restart the content server.
|
Note: You should be aware, however, that the system performance will decrease with the increased number of items that you have in a folder. |
This section covers the following topics:
Question
How can I stop the automatic import function?
Recommendation
When content meets the specified criteria, the automatic importer is, by default, configured to automatically perform an import every five minutes. However, there are two ways to disable the automatic import function:
To unregister an importer from the Replication tab, complete the following steps:
Log into the source content server as an administrator.
Go to the Administration page and click the Archiver link.
The Archiver utility is started.
Select the archive in the Current Archives list.
Open the Replication tab.
Click Unregister.
The automatic import function is disabled from the selected archive.
To delete a registered importer from the Automation for the Instance screen, complete the following steps:
Log into the source content server as an administrator.
Go to the Administration page and click the Archiver link.
The Archiver utility is started.
Select Options and then View Automation For Instance.
The Automation For Instance screen is displayed.
Open the Importers tab.
Select the registered importer to delete.
Click Remove.
The registered importer is removed from the list.
This section covers the following topics:
Symptom
I cannot transfer files. Every time I try to transfer files, I get 'max extents' error messages.
Problem
The following error messages (or similar) are issued:
IdcApp: Unable to execute query '<query_name>'. Error: ORA-01631: max # extents (50) reached in table <table_name>. ORA-01631 max # extents (<text_string>) reached in table <table_name>.
Recommendation
When the content server creates its database tablespace, it only allocates 50 extents. As the database grows and is re-indexed, it uses more space (extents). Eventually, the 50 extents limit is exceeded. At some point in the transfer, one of your files tried to extend past the 'max extents' limit. In this case, try implementing one or more of the following solutions:
Look for weblayout queries that are excessively large, eliminate them, and retry your transfer.
Perhaps a Content Server user does not have the right permission grants (resource and connect) to the content server schema. That user must have the temporary tablespace and default tablespace set to the content server defaults.
If the system 'max extents' limit is less than the system maximum, you must increase the number of extents that are available. Refer to your Oracle documentation or ask your database administrator for the appropriate Oracle SQL command to increase the tablespace extents.
You can optionally choose to re-create the database using larger initial, next or percent to grow parameters for the tablespaces. In this case, it is advisable to set the initial extents and next extents to 1Mb. Set the percent to grow parameter (PCTINCREASE) to 0% to allow the tables to automatically grow on an as-needed basis.
This section covers the following topics:
Symptom
I am trying to transfer between two content servers with access to a shared file system but it is not working.
Recommendation
When transferring between content servers on a shared file system, the mapped or mounted drive must be available to both content servers. This means that the computers must be on and logged in as a user who has system access to both content servers. Make sure that all of the following conditions are met:
Both computers are turned on.
Both computers are logged in as a user with system access to both content server file systems.
The shared drive has been properly mapped or mounted so the content server can "see" it. Having network access to the computer is not sufficient.
Symptom
I am trying to transfer between two content servers over an outgoing provider but it is not working.
Recommendation
The content server that has an outgoing provider set up is considered the 'local' server, and the target content server for the outgoing provider is considered to 'proxied' server. Files are always transferred in the direction of the outgoing provider, from the local (source) instance to the proxied (target) instance.
It is possible that when the outgoing provider was added and defined for the source content server, the Proxied check box was selected. However, because the relative web root is the same for both content servers, the outgoing provider is confused. The Proxied check box should be selected only if the target content server was installed as an actual proxy of the local (master) content server. This server option should not be selected if the relative web root is the same for both content server.
