Deployment '2700002' to target 'tar152' encountered a system level deployment error during data transfer.

Question

Hi All,
I got this error in atg bcc on UI and console as well when i doing full deployment.
I triyed through snap-shot id but i think this is different issue.
So please tell me where is problem happend.
Thanks in Advance.
--Kakasaheb.

Answer 1

Are you working with a customer with a support contract?
Cause
One potential cause is corrupted data in the epub_file_folder table in the versioned schema and examining the table contents is necessary.  This data may be the result of a deployment containing VFS assets that did not complete successfully
The BCC application assumes that the virtual folder structure contained in epub_file_folder is built upon a single root folder.  This folder has the name 'root' and has a NULL parent_folder.  If another folder in this table has a NULL parent_folder, then the application does not know which is the true root folder.  As a result, based purely on chance, the BCC will choose one of them as the root folder of the VersionFileStore (VFS).  Depending on which assets are contained beneath that folder, some file assets may not appear correctly in the BCC UI.  Another symptom is the inability to deploy any project, including a full deployment.
To check for this particular corruption, perform the following SQL query.
select * from epub_file_folder order by parent_folder;
Putting the table data in a spreadsheet makes it easier to sort the data on various columns for analysis.
If you sort by parent_folder check for data similar to that shown in the following table.  Note that there are two folders whose parent_folder is NULL. Here are the relevant columns from epub_file_folder:
folder_id
folder_name
parent_folder
asset_version
is_head
version_deleted
version_editable
ff102063
CorruptFolder
NULL
1
1
0
0
root
root
NULL
1
1
0
0
Solution
Note:  Exercise caution when directly modifying the versioned database schema.  For assistance identifying this problem and implementing the solution, please open an SR with Oracle Support.
1. Analyze Versioned Folder Data
How you resolve this corruption will depend on whether or not you need to retain the corrupt folder.  Examine whether the folder has an asset version that is checked in, marked as deleted, or marked as the head version.  If there is no checked-in version with is_head=true, then this indicates the folder may have been part of a failed deployment.
Trace through the hierarchy of folders underneath the corrupt folder.  Determine whether there are any folders or files within that hierarchy that you need to retain.  In some cases, it may be a single folder created unintentionally by a BCC user.  In other cases, there may be more significant folder structure underneath it that is needed by the front-end application.
2a. Corrupt Folder Not Needed
If you do not need the corrupt folder, set its version_deleted=1.
This will mark the folder as Deleted in the versioned repository.  As far as the BCC is concerned, neither it nor anything under it will exist and will not appear in the BCC UI.  The data will still be retained in the database, though.
2b. Corrupt Folder Needs Correct Parent
If you do need the corrupt folder, determine the true parent folder.  Set its parent_folder to the ID of the actual parent.
See the folder_id column for the correct parent folder and substitute that ID for NULL in BadFolder's parent_folder.
3. Restart BCC and Re-Test
After modifying the data for the corrupt folder, restart the BCC so that the repository picks up all the changes.
++++
Thanks
Gareth
Please mark any update as "Correct Answer" or "Helpful Answer" if that update helps/answers your question, so that others can identify the Correct/helpful update between many updates.