Archive removed

Hi,
we removed some archive logs and after that we have this error message in RMAN backup report :
RMAN-03002: failure of backup command at 11/07/2006 14:27:51
RMAN-06059: expected archived log not found, lost of archived log compromises recoverability
ORA-19625: error identifying file /oracle/archive/Database/1_60287.dbf
ORA-27037: unable to obtain file status
IBM AIX RISC System/6000 Error: 2: No such file or directory
Additional information: 3
My questions :
1-are backups safe ?
2-What to do to not to have this error messages ?
many thanks.

Did you backup the archive logs with RMAN or did you manually remove them?
If you manually removed them, then your ability to recover the database will be compromised as the recovery process might need the missing archive logs.
How are you backing up the database with RMAN currently? You might want to consider adding a step to backup up the archive logs and purge them after the backup.
To remove the error you are receiving about the missing logs you can issue the following in RMAN
CROSSCHECK ARCHIVELOG ALL;

Similar Messages

Archiving - removal of deletion indicator on p.o. item line

Hi all,
we've run into some problems in 4.7 with old p.o.'s which have been delete marked of the archiving program (step 1 - residence time one), where the user now want's to remove the deletion mark again, - but this is not possible, as the purch. req. has already been archived :o(
Example:
Purchase orders have a residence time as follows:
Residence time 1:       30 days
Residence time 2:       395 days
Purchase requisitions have a residence time as follows:
Residence time 1:       30 days (we're having a one step archiving procedure for MM_EBAN)
Now the p.o. has got a delete mark on item line according to residence time 1 = 30 days (MM_EKKO) and afterwards the purch. req. has been archived (according to residence time 1 = 30 days (MM_EKKO). The user can't manually remove the deletion mark from the p.o. item line again, because of an error saying "purchase requisition xxx, item xxx does not exist"
What can we do, to remove the delete mark from the p.o. item line again - can the link between the p.o. and the archived purch. req. be removed ?
Thanks in advance for your reply :o)
Best regards/Med venlig hilsen
Ulla Köhler Hansen
Application Consultant, SAP R/3 - SRM/PLM Solutions
The Danfoss Group
Danfoss Information Technology
Loc. 1.0.53
Ellegaardvej 25 A
DK-6400 Sønderborg
Denmark
Tel.: + 45 7488 3913
Fax: + 45 7488 4715
e-mail: [email protected]
http://www.danfoss.com/
This message and any files transmitted with it may be confidential and are intended only for
the individual named. If you are not the named addressee you should not disseminate, distribute
or copy this e-mail. Please notify the sender immediately by e-mail if you have received
this e-mail by mistake and delete this e-mail from your system.

Hi
I have made the change in your code , try this code .
it_bapimepoitem-po_item = '00100'.
*it_bapimepoitemx-po_item = 'X'.*
it_bapimepoitem-DELETE_IND = ' '.
it_bapimepoitemx-DELETE_IND = 'X'.
APPEND it_bapimepoitem.
APPEND it_bapimepoitemx.
Hope it will help you .
Regards
Rahul

Archive/remove attachments but keep link to file in emails

Hello,
I have been browsing and googling extensively but didn't find a solution for what I am trying to do:
I have quite a large email folder in the ~/Library (around 90GB+) and I am trying to reduce that size.
For this I want to remove all or most of the attachments (or at least the biggest ones).
Removing and saving the attachments to a folder is pretty easy.
Once the attachment is removed from the email, I would like to be able to go back to this email and see a mention that (for example):
'The attachment has been removed on [Date] at [Time]"
with mention of the files names, the path at the time of the saving and for each file a link to the saved location on the disk.
Is there any way to do that?
Any software or mail plugin??
Any help would be appreciated,
Thanks in advance
Eric

Hi Sarah,
Thanks for the reply.
What my clients want to accomplish is is to package all the separate .js files for the website into one file, so all the pages load faster.
This includes the Animate.js files which are only to be used for the home page, so of course random animations appear on the rest of the pages which don't have the animate DIVs in them.
I have suggested they package all the .js files EXCEPT the animate.js ones and just load them separately on the page the animations are to appear on.
But they are still wanting to do them all in one package however (!!) so my question is:
Can some code be added to the animate.js files that says something like "if these DIVs are not found, make the animation do nothing"?
It is possible the relevant code cannot be added in which case they will have to do the animate.js files separately, but as they have asked me about it I thought I would ask people in the forum if they knew how to accomplish this.
Cheers,
Jim

Diff. between content server and archive server(SARA on content server)

I am very interested about difference between content server and archive server. Is there content server supplied by SAP and archive server by third party producers or something else?
If so dditionally what needs to be done to archive data (via Sara) on content server. I did it on sap R/3 4.0 on an archive server. Is it huge difference to do it on 4.7x2 on content server?

Hey,
The content server is used to save documents,
and SARA (and other third party producers) are used to archive old data.
For example:
You should use Content server - When you need to save un-structured data about worker (e.g: pictures, documents and etc) .
You should use SARA (and other third parties) - When you need to move to archive old
worker which have left your organization before 5 or more years (there for they are not relevant for you)
Here is some more information about Content server
from help.sap.com:
"Therefore, besides the SAP database, an external content server is always available in every SAP system installation. In this way, the necessary technical infrastructure is provided for all document-centric applications and business scenarios that do not require a long-term archiving solution"
Here is some more information about SARA and archiving
from help.sap.com:
"Data Archiving removes from the database application data from closed business transactions that are no longer relevant for the operational business. The archived data is stored in archive files that can be accessed by the system in read-only mode."
for more information:
http://help.sap.com/saphelp_nw70/helpdata/en/8c/e9ddbb5d9a524bbb7854d31b963248/frameset.htm
http://help.sap.com/saphelp_nw70/helpdata/en/73/c335406ee32e34e10000000a155106/frameset.htm

Would you like help me regarding archiving please .. ?

Dear All,
We're in the archiving project ..
We here have scenario to reload/restore archived data from BW Production to BW Development server ...
I did try it: I moved the archived file to archived known storage in BW Development, but it didn't recognize it ..
My questions:
1. Is it possible to get the scenario be done ??? How can i make it ??
2. I run t-code AOBJ and found that there is reload program (e.g. of the program: SBOOKL), What is it for ?? Could this program solve my case above ??
Really need ur guidances all.
Best regards,
Niel.

Data Archiving
Data Archiving u2013 a service provided by SAP u2013 removes mass data that the system no longer needs online, but which must still be accessible at a later date if required, from the database.
Data Archiving removes from the database application data from closed business transactions that are no longer relevant for the operational business. The archived data is stored in archive files that can be accessed by the system in read-only mode.
The following graphic illustrates the archiving process:
Reasons for Archiving
There are both technical and legal reasons for archiving application data. Data Archiving:
Resolves memory space and performance problems caused by large volumes of transaction data
Ensures that data growth remains moderate so that the database remains manageable in the long term
Ensures that companies can meet the legal requirements for data storage in a cost-efficient manner
Ensures that data can be reused at a later date, for example, in new product development
Data Archiving Requirements
Data archiving is intended to do more than simply save the contents of database tables. Data archiving must also take the following requirements into consideration:
Hardware independence
Release dependence
Data Dependencies
Enterprise and business structure
Optical Archiving
The term u201Coptical archivingu201D generally describes the electronic storage and management of documents in storage systems outside of the SAP Business environment. Examples of documents that can be stored in this way include:
Scanned-in original documents, such as incoming invoices
Outgoing documents, such as invoices created in mySAP Financials that are created electronically, then sent in printed form
Print lists created in mySAP Business Suite
Residence Time and Retention Periods
The residence time is the minimum length of time that data must spend in the database before it meets the archivability criteria. Residence times can be set in application-specific Customizing.
The retention period is the entire time that data spends in the database before it is archived. The retention period cannot be set.
Ex: If the residence time is a month, data that has been in the system for two months will be archived. Data that is only three weeks old remains in the database.
Backup & Restore
Backup is a copy of the database contents that can be used in the case of a system breakdown. The aim is that as much of the database as possible can be restored to its state before the system breakdown. Backups are usually made at regular intervals according to a standard procedure (complete or incremental backup).
Reloading the saved data into the file system is called restoring the data.
Archiving Features
Data Security
Data archiving is carried out in two steps (a third step u2013 storage of archive files u2013 is optional: In the first step, the data for archiving is copied to archive files. In the second step, the data is deleted from the database. This two-step process guarantees data security if problems occur during the archiving process.
For example, the procedure identifies network data transfer errors between the database and the archive file. If an error occurs, you can restart the archiving process at any time because the data is still either in the database or in an archive file. This means that you can usually archive parallel to the online application, that is, during normal system operation, without having to back up the database first.
You can further increase data security if you store the archive files in an external storage system before you delete the data from the database. This guarantees that the data from the database will only be deleted after it has been securely stored in an external storage system.
Data Compression
During archiving, data is automatically compressed by up to a factor of 5. However, if the data to be archived is stored in cluster tables, no additional compression takes place.
Storage Space Gained
Increased storage space in the database and the resulting performance gains in the application programs are the most important benefits of data archiving. Therefore it is useful to know how much space the data to be archived takes up in the database. It may also help to know in advance how much space the archive files that you create will need.
Note: - Data is compressed before it is written to the archive file. The extent of the compression depends on how much text (character fields) the object contains.
Archiving without Backup
With SAP Data Archiving, data can be archived independently from general backup operations on the database. However, SAP recommends that you backup archive files before storing them.
Accessing Archived Data
Because archived data has only been removed from the database and not from the application component itself, the data is always available. Archive management allows three types of access:
1.     (Read) access to a single data object, such as an accounting document
2.     Analysis of an archive file (sequential read)
3.     Reload into the database (not possible for all archiving objects)
Converting Old Archive Files
When archived data is read, the system automatically makes the conversions required by hardware and software changes.
When old archive files are accessed, the Archive Development Kit (ADK) can make allowances for changes to database structures (field types, field lengths, new fields, and deleted fields) after the data was archived and for changes to hardware-dependent storage formats. This is only done on a temporary basis during read access. The data in the archive file is not changed. The following items are changed (if necessary) during automatic conversion:
Database table schema (new and deleted columns)
Data type of a column
Column length
Code page (ASCII, EBCDIC)
Number format (such as the use of the integer format on various hardware platforms)
If database structures in an application have undergone more changes than the ADK can handle (for example, if fields have been moved from one table to another or if one table has been divided into several separate tables), then a program is usually provided by the relevant mySAP Business Suite solution for the permanent conversion of existing archive files.
Link to External Storage System
Archive files created by Data Archiving can be stored on tertiary storage media, such as WORMs, magnetic-optical disks (MO), and tapes using the SAP Content Management Infrastructure (which also contains the ArchiveLink/CMS interface). This can be done manually or automatically.
You can also store archive files in the file system of an HSM system. The HSM system manages the archive files automatically. For storage, the HSM system can also use tertiary storage media, such as MO-disks.
CMI/R u2013 Content Management Infrastructure / Repository
HSM u2013 Hierarchical Storage Management Systems
Archiving Procédure
The basic Archiving procedure is carried out in three steps,
Creating the Archive Files
Storing Archive Files
Executing the Delete Programs
Security Vs Performance
Optionally, you can store archive files after the delete phase. To do this, you must mark Delete Phase Before Storage in archiving object-specific Customizing.
If security is your main concern, then you should not schedule the delete phase until after the archive files have been stored. In this way you know that the data will only be deleted from the database after the archive files have successfully been moved to the external storage system. In addition, you can set the system to read the data from the storage system and not from the file system.
However, if your main concern is the performance of the archiving programs, then you should schedule the delete program first and then store the files.
Creating Archive Files (WRITE)
In step one, the write program creates an archive file. The data to be archived is then read from the database and is written to the archive file in the background. This process continues until one of following three events occurs:
All the data is written to an archive file
Archiving is not complete, but the archive file reaches the maximum size specified in archiving object-specific Customizing
The archiving is not yet finished, but the archive file contains the maximum number of data objects specified in Customizing.
If in cases 2 and 3 there is still data to be archived, the system will create another archiving file.
Storing Archive Files (STORE)
Once the write program has finished creating archive files, these can be stored. There are several ways of storing archive files:
Storage Systems:
If a storage system is connected to mySAP Business Suite: At the end of a successful write job, a request is sent to this system to store the new archive files (provided the appropriate settings were made in Archiving Object-Specific Customizing. You can also store archive files manually at a later point if you do not want them to be stored automatically. Storage is carried out by the SAP Content Management Infrastructure (which contains the ArchiveLink/CMS interface).
HSM Systems:
If you use an HSM system, it is sufficient to maintain the file name in Customizing (Transaction FILE). You do not then need to communicate with the storage system using the SAP Content Management Infrastructure, because the HSM system stores the files on suitable storage media according to access frequency and storage space.
Existing Storage Media:
Once the delete program has processed the relevant archive file, you can manually copy archive files to tape.
Running Delete Programs
After closing the first archive file, the archive management system creates a new archive file and continues with the archiving process. While this happens, another program reads the archived data from the completed archive file and deletes it from the database. This procedure guarantees that only data that has been correctly saved in the archive file is deleted from the database.
If you do not carry out deletion until after the data has been stored, you can make a setting in Archiving Object-Specific Customizing so that the system will read archive files the from the storage system during deletion. In this way, you can detect errors in good time which might arise when transferring or saving the archive files in the storage system.
When the last archive file is closed, a delete program starts to run for this file. The graphic shows that several delete programs are running simultaneously for previously created archive files. Because, unlike the delete program, the write program does not generally carry out any transactions that change data in the transactions, the write program creates new archive files faster than they can be processed by the delete program. This decreases the total archiving runtime because the database is used more efficiently.
Note:-
Scheduling the Archive jobs outside SARA
WRITE:-
Using an external job scheduler (SM36, SM62)
WRITE Run followed by EVENT - SAP_ARCHIVING_WRITE_FINISHED,
Parameter is Session Number
To analyze the archiving information of a particular session, use FM
     ARCHIVE_GET_FILES_OF_SESSION
     Input is Session Number
DELETE:-
Using an external job scheduler (SM36, SM62)
Using program RSARCHD, input u2013 Obj Name, Max. no. of files, Max no. of sessions, Max no. of jobs,
          Background User
DELETE run followed by EVENT - SAP_ARCHIVING_DELETE_FINISHED
     Parameter is Session Number
To analyze the archiving information of a particular session, use FM
     ARCHIVE_GET_FILES_OF_SESSION
     Input is Session Number
Archiving Object
The archiving object is a central component of SAP Data Archiving. The archiving object specifies precisely which data is archived and how. It describes which database objects must be handled together as a single business object and interprets the data irrespective of the technical specifications at the time of archiving (such as release and hardware).
Note:-
     An archiving object has a name of up to ten characters in length.
     Transaction code to maintain the Archiving Object is AOBJ.
The following programs must (or can) be assigned to an archiving object. The SAP System contains programs (some of which are optional) for the following actions:
Preprocessing (Optional)
Some archiving objects require a preprocessing program that prepares the data for archiving. This preprocessing program marks data to be archived, but it does not delete any data from the database. Preprocessing programs must always be scheduled manually and are run from Archive Administration.
Write
This program creates archive files and writes data to them. At this point, however, no data is being deleted from the database.
You can specify in archiving object-specific Customizing whether the next phase (delete) is to take place automatically after the archive files have been created. Delete jobs can also be event-triggered. To do this, you set up the trigger event in archiving object-specific Customizing.
Delete
This function can entail several activities. The activities are always dependent on the existing archive files. Normally, the data is deleted from the data base. However, in some case, the archived data in the database may only have a delete indicator.
In archiving object-specific Customizing, you can specify that archive files, after successful processing, are to be transferred to an external storage system using the SAP Content Management Infrastructure (which contains the ArchiveLink/CSM interface).
Postprocessing (Optional)
This function is usually carried out after deletion has taken place. It is not available for all archiving objects. If the data has not yet been deleted from the database by the delete program, it is deleted by the postprocessing program.
Reload Archive (Optional)
You can reload archived data from the archive files into the database using this function. It is not available for all archiving objects. To access this function, choose Goto ® Reload.
Index (Optional)
This function builds (or deletes) an index that allows individual access. It is not included in every archiving object.
Data Object
A data object is the application-specific instance of an archiving object, that is, an archiving object filled with concrete application data. The Archive Development Kit (ADK) ensures that data objects are written sequentially to an archive file. All data objects in an archive file have the same structure, which is described in the archiving object.
Archive Administration (SARA)
All interaction relating to data archiving takes place in the Archive Administration (transaction SARA). Features of Archive Administration:
Preprocessing
     Write
     Delete
     Postprocessing
     Read - Enables you to schedule and run a program that reads and analyzes archived data.
     Index
     Storage System - Enables archive files to be transferred to a connected storage system and
                                         enables stored archive files to be retrieved from a storage system.
     Management - Offers an overview of archiving sessions for one archiving object.
Depending on the action you have selected, you can use Goto on the menu to access the following menu options:
     Network Graphic
     Reload
     Customizing
     Job Overview
     Management
     Stored Files
     Database Tables
     Infosystems
     Statistics
     Interrupting and Continuing
Archive Development Kit
The Archive Development Kit (ADK) is a tool for developing archiving solutions. It also prepares the runtime environment for archiving. From a technical viewpoint, it is an intermediate layer between the application program and the archive that provides all the functions required for archiving data.
The ADK functions are required for archiving and for subsequent access to archived data. The ADK automatically performs the hardware-dependent adjustments (such as code page and number format) and structural changes that are required when archive files are created. When the archive files are accessed later, the ADK temporarily converts data that was archived using earlier SAP releases.
Note:-
S_ARCHIVE is the SAP delivered user authorization check object over archiving objects. The Archive Development Kit (ADK) performs the check when an archive file is opened for one of the following actions:
Write
Delete
Read
Reload
Database Tables in Archive Administration (DB15)
This enables you to display all of the tables for a specific archiving object and as well as allows to display the list of Archiving Objects on a particular database table. Also enables to display the storage and space statistics. This also provides further information, such as the time and number of the last archiving session and various details on the client used.
Network Graphic
You can use the network graphic to show any existing dependencies between archiving objects. It shows business process flows and contexts that can influence the archiving sequence. In particular, at the start of an archiving object, you can use the network graphic to obtain a good overview of related documents.
In an archiving session, you must take into account any dependencies between archiving objects that require a specific archiving sequence. In general, you cannot archive data for an archiving object that has preceding objects until these preceding objects have been archived.
You can use the network graphic to determine whether the archiving object that you want to use has preceding objects. If so, the preceding objects should be implemented before the current archiving object. The nodes in the network graphic represent the archiving objects. A node displays the following information:
Archive Object Name
Application Component Name
Short Description
Date of last archiving
Status of the session
     If status is u2018Greenu2019
     Archiving and Deletion is Successful
     If status is u2018Yellowu2019
     Successfully archived, but not yet deleted, or Archiving still running, or Delete in progress or
Delete Cancelled
If status is u2018Redu2019
Not yet archived, or Archiving cancelled
Standard Log (Spool List)
During archiving, a log is usually generated. This can be done during the write, delete, read, or reload phases. This is usually in the form of a standard log. In some cases, an application-specific log may be generated. Depending on the archiving action that was carried out, the standard log contains statistical information per archiving session or archive file according to the following categories:
Archiving session number
Number of data objects for processing
Archive session size in megabytes
Total header data in %
Table space in MB occupied for:
          Tables
          Indexes
Number of table entries processed
You can call the standard log from the screen Archive Administration: Overview of Archiving Sessions. Choose Spool List.
Accessing Archived Data
Data that was archived using SAP Data Archiving has been relocated from the database but not placed beyond the application. Data is still available for read access and analysis. In some cases, archived data can even be reloaded into the database.
Note:-
A prerequisite of read access and reload access, is that the file can be found in the file system.
Three types of access are possible:
(Read) access to a single data object, such as an accounting document
Direct access or single document access requires an index that can be built either during archiving or at a later point. A complex search of the documents stored in the archive files, in which all orders of an article in a particular batch are required for a product recall action, is not possible.
The Archive Information System (AS) supports direct access using archive information structures that can be generated automatically either when the archive files are being written, or at a later point.
Analysis of an archive file (sequential read)
It is possible to run an analysis for one or several archiving sessions. The results of the analyzed data objects are displayed in a list. Furthermore, some archiving objects offer the option of a combined analysis. With this option, you can link current data in the database and archived data.
Reloading into the database
Archived data does not usually need to be reloaded because it remains accessible by the applications. There is also a lot of data that cannot be reloaded or for which reloading is problematic. For this reason, reload programs do not exist for all archiving objects.
Archiving Session Overview
On this screen, you can display and edit management information on archiving sessions. One archiving session is equal to Write and Delete jobs. Within a status area, archiving sessions are, by default, organized in groups of 20. The sessions are ordered according to different status.
Interrupting and Continuing
In order that Data Archiving can be seemlessly integrated into the production system, you can interrupt an archiving session during the write phase and contine it at a later time. This enables you to react, during archiving, to specific time constraints or hard-disk space shortages. You can continue and complete interrupted archiving sessions when you have more time or more storage space.
To interrupt an archiving session:
The archiving object must be registered in transaction AOBJ as interruptible, otherwise the Archive Development Kit (ADK) is unable to inform the write program of the interruption request.
The write program must be able to process the interruption request.
The archiving session must be run in production mode (not test mode) and be in process.
The delete phase must be able to start before the write phase has finished (setting in transaction AOBJ).
To continue an archiving session:
The session must have been interrupted within the context of the interrupution concept. Archiving sessions that were interrupted for other reasons or that were terminated by archive management cannot be continued.
The delete phase must have completed for the data that was archivied up to the point of interruption, that is, the archiving session must have the status completed.
Database Action Before and After Archiving
Archiving uses application software that depends on and affects the organization of the database data. You should therefore organize the database before and after archiving.
Before Archiving
Archiving application data helps to prevent storage and performance bottlenecks. Since relocating data can, in some circumstances, in itself, impair performance u2013 this is the case if you need to access archived data u2013 you need to consider carefully what data to archive. To determine whether or not you should archive data, consider the following questions:
If there are memory problems, can more memory be assigned to the table?
How likely is it that you will need to access the archived data again? How often?
Is the data accessed using an optimal index?
Does the application perform a full table scan on the tables that contain the data to be archived?
After Archiving
Reorganize index: If data has been archived or simply deleted and the associated tables were accessed via an index, the index should be reorganized. Deleting table entries leaves holes in the table which are still indexed. Reorganization can shorten the access paths, reducing response times.
Update the database statistics: If your database uses a cost-based optimizer, you must choose Update Statistics to recalculate the access paths.
Reorganize tablespace or database space: Whether you should reorganize the tablespace depends on the reason for archiving.
Do you expect a lot of new data for the archived tables?
Do you want to make space for other tables?
Note:-
Reorganization takes a long time and may need to be repeated after archiving. Throughput during a reorganization:
     With export/import     :           approximately. 60-100 MByte/hour.
       With unload/load     :           approximately. 250-300 MByte/hour.
Perform an SQL Trace after reorganization.
Statistics
When writing, deleting, reading, or reloading, statistical data on each archiving run is automatically generated and is persistently stored in the database The data archiving administrators can analyze these figures so that they can better plan future archiving projects and request the necessary resources. Statistics also provided pertinent information on the role of data archiving in reducing the data volume in the database.
You can call this screen directly from the Archive Administration (SARA), or using the transaction SAR_DA_STAT_ANALYSIS. It displays the following information:
     Archiving Session Number
     Archiving Object Name
     Client ID on which the archiving session was carried out
     Date on which the archiving session was carried out
     Status of the session number
     Portion of the Header data in the archiving session
     DB Space (WRITE) u2013 Virtual storage space in MB, which is occupied by an incomplete archiving                          session in the database
     DB Storage Space (DELETE) - Virtual storage space in MB, which is occupied by an incomplete                               archiving session in the database
     DB Space (Reload) u2013 Virtual storage space in MB
     Written Data Objects in an incomplete archiving session
     Deleted Data Objects for an incomplete archiving session in database
     Reloaded Data Objects
     Number of delete jobs
     Write job duration
     Delete job duration
     Reload job duration
Logical Path and File
Archive files are stored in the file system under a physical path and file name that is derived from a user-definable logical path or file name. The definition can be divided into the following steps:
Definition of the logical path name
Definition of the logical file name
Assignment of the logical fine name for the archiving object
By default, the system uses the logical file name ARCHIVE_DATA_FILE and the logical path name ARCHIVE GLOBAL PATH as defaults. Consequently, the names only need to be changed if they have to be adjusted to meet special requirements.
Data Archiving Monitor
Use this indicator to activate or deactivate the data archiving monitor (transaction SAR_SHOW_MONITOR. If you mark this checkbox before data archiving, archiving-relevant information on the write and delete jobs is updated. This information can be analyzed using the data archiving monitor. If there are errors, alerts are issued.
The data archiving monitor offers the following information:
Overview of all the archiving objects that have been run
Detailed information on the individual archiving sessions
Processing status display
Help on analyzing open alerts

While mat .doc archiving error

Hi
While mat .doc archiving i am getting error can not be archived due to Document
not completed.
How to find what are all the documents and how to correct the same ?
Thanks
Regards,
Dhinesh

Dear,
Please go through the below:
Archiving (transaction SARA)
Data archiving removes bulk data which is no longer required in the System, but which must be retained accessibly, from the database. Data in the R/3 database can only be archived via archiving objects, which describe the data structure. Financial accounting documents, for example are archived via the archiving object FI_DOCUMNT, which comprises the document header, company-code-dependent postings, change documents, SAPscript texts and other elements. The application archiving objects are pre-defined in the system. The archiving programs are scheduled as background jobs, but can run during on-line processing. The system need not be shutdown.
The archiving procedure comprises two main steps:
Create archive files: the data to be archived are first written sequentially into a newly created file. The data then exist twice in the database. These archive files can, e.g. be passed to an archive system, via ArchiveLink.
Execute delete program: the data in the archive files are removed from the database by the delete program.
You can check how the archive filenames and archive destination are setup in transaction FILE
Always remembers to check the setting before any archiving. The settings will determine things like whether the delete programs will start automatically. (it is not advisable to start your delete programs automatically).
You can configure all the customizing settings with transaction AOBJ - Archive Objects.
MM_MATBEL - Archive material document
OMB9 - Archiving - Material document retention period.
The default documents life is 200 days. You need to maintain the documents life for each Plant in your company before you can start archiving. If you did not maintain, you will get a list with 'Valid.period not maintained for tr./ev. type of doc.'.
MM_ACCTIT - Archive accounting interface tables
The documents store in the table are for applications which are to be supplied with the posting data at a later date of MM Inventory Management and MM Invoice Verification.
If you are using 3.x, this archiving object might not be found. You need to import it from sapservX. Read note 89324, 99388, 83076.
Take a look at OSS note 48009 for the detail explanation of which data is updated in the ACCT* tables.
PP_ORDER - Archive production order
OPJH - Production Order retention period. Maintain Retention 1 and 2.
If your set your retention 1 and 2 as 10, that means that after 10 days of setting the delete flag then you can set the deletion indicator. After 10 days of setting the deletion indicator then you can start archiving. Therefore, to archive immediately, you can leave retention 1 and 2 as space. Please take note that retention 1 and 2 act as a safety net if you happened to archive the wrong record. You will have to decide whether to have the retention time gap or not.
FI_DOCUMNT - Archive Financial Accounting Documents
Maintain the account life - transaction OBR7
Maintain the documents life - transaction OBR8
SD_VBRK - Archive Billing Documents
There are no posting date or fiscal year/period selection. You can only specify the billing documents date. In order that you do not archive the wrong record, you have to write a ABAP query or report to print out the various billing documents number ranges you want to archive. You can extract the data from table
VBRK - Billing: Header Data.
VN01 - Check all the number ranges for Billing Documents.
Click Overview buttom or Hold the Shift key and press F7.
RV_LIKP - Archiving Deliveries
VORL - Maintain the retention period. Number of days which must have elapsed since the delivery was created, before the delivery can be archived.
VLAL - Archive deliveries
Regards,
Syed Hussain.

Archiving ECM

Hello Gurus,
I reviwed all the PP archiving objects/tables for BOM, Workcenters, Routings, Production orders, Process orders and Backflushing. I couldn't find any information related to ECM archiving.
Could you please let me know how Engineering Change Orders can be archived.
We are currently using 4.6c.
I appreciate your help.
Thanks in advance
Srini

Dear Srini
Use T-CODE : SARA and Archiving Object :LO_CHANGEM
SOME TIPS:
Archiving (transaction SARA)
Data archiving removes bulk data which is no longer required in the System, but which must be retained accessibly, from the database. Data in the R/3 database can only be archived via archiving objects, which describe the data structure.
The archiving procedure comprises two main steps:
Create archive files: the data to be archived are first written sequentially into a newly created file. The data then exist twice in the database. These archive files can, e.g. be passed to an archive system, via ArchiveLink.
Execute delete program: the data in the archive files are removed from the database by the delete program.
You can check how the archive filenames and archive destination are setup in transaction FILE
Always remembers to check the setting before any archiving. The settings will determine things like whether the delete programs will start automatically. (it is not advisable to start your delete programs automatically).
customizing settings with transaction AOBJ - ECM Object LO_CHANGEM
Regards
Narayana

Delivery archived

Hi,I checked the document flow of one billing document via t-code: VF03, and it shows as follows:
Document Date Overall processing status
. Delivery 1000514964 Archived <<<----
Invoice 90454051 06/08/15 Completed
. Accounting document 8600041838 06/08/15 Cleared
My question is, what's the meaning of 'Archived' to the delivery number 1000514964, what kind of operation could caused its status become to 'Archived'?
Please kindly help.
Best Regards.

Hi Ren,
It seems the delivery document 1000514964 has been archived/removed from database application data
and placed in archive file that can be accessed and analyzed at a later date/in the future.
For more information on application data archiving, please check this online document.
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CAARC/CAARC_INTRO.pdf
Hope this will help.
Regards,
Ferry Lianto

Removing a deployed project

Hello. How do you remove or uninstall a deployed portal webdynpro project or application in portal?

Hi There !
Yes you can UnDeploy the WebDynpro Project.
Follow this Procedure.
1.Log on to the Portal.
2.Navigate to Java DeveloperToolsPortal Archive Deployer and Remover.
3.In the Right hand Pane you will Find Archive Remover.
4.Select the Project From the DropDown and Click Clean .
Thats it.
Cheers !
Regards,
Rajendra

Remove PDK 6.2

Hi everyone,
I am new to all SAP Netweaver thing, so my questions might have some "obvious" answers, but I just dont seem to find them.
I installed EP6 SP6. Than following one of the e-learning courses provided by SAP I tried to install PDK (but i think I choose the wrong version 6.2, instead of 6.6). Now I want to uninstall 6.2, and install 6.6, but I dont really know where to start... After I read some posts on this forum, I thought that the right way to do it would be Archive Remover, but there i see many packages com.sap.portal.pdk*. I am not sure if is right to remove these all without damage something in the portal.
Any help or further hints would be highly apreciated.

Hi Noel and thanks for the answer.
I also thought of this, but I saw some postings saying that the best practice would be to remove the previous version without installing the new one. Another issue would be: I tried to run TemplateJSPDynPage...I downloaded the par file from the portal, I imported in into eclipse but than I get 25 errors. I think this was from the missing libraries, so I downloaded the libraries from the portal and I imported in eclipse html.jar but: Than I still have 11 errors which I think are because of the missing htmlbridge.jar but I cannot find this jar. Kind     Status     Priority     Description     Resource     In Folder     Location
Task     Not Completed     Normal     TODO : Implement     FirstsessionbeanBean.java     myfirstejbmodule/ejbModule/myfirstpackage     line 33
Error               The import com.sapportals.portal.htmlb cannot be resolved     TemplateJSPDynPage.java     myJSP/src.api     line 28
Error               The import com.sapportals.portal.htmlb cannot be resolved     TemplateJSPDynPage.java     myJSP/src.api     line 29
Error               PageProcessorComponent cannot be resolved or is not a valid superclass     TemplateJSPDynPage.java     myJSP/src.api     line 45
Error               Type mismatch: cannot convert from TemplateJSPDynPage.RealJSPDynPage to DynPage     TemplateJSPDynPage.java     myJSP/src.api     line 60
Error               JSPDynPage cannot be resolved or is not a valid superclass     TemplateJSPDynPage.java     myJSP/src.api     line 67
Error               The method getRequest() is undefined for the type TemplateJSPDynPage.RealJSPDynPage     TemplateJSPDynPage.java     myJSP/src.api     line 126
Error               The method getComponentByName(String) is undefined for the type TemplateJSPDynPage.RealJSPDynPage     TemplateJSPDynPage.java     myJSP/src.api     line 180
Error               The method setJspName(String) is undefined for the type TemplateJSPDynPage.RealJSPDynPage     TemplateJSPDynPage.java     myJSP/src.api     line 201
Error               The method setJspName(String) is undefined for the type TemplateJSPDynPage.RealJSPDynPage     TemplateJSPDynPage.java     myJSP/src.api     line 205
Error               The method setJspName(String) is undefined for the type TemplateJSPDynPage.RealJSPDynPage     TemplateJSPDynPage.java     myJSP/src.api     line 209
Do you know what am I doing wrong here, or what should I do? I am new to this technology and I am a little bit confused....
Thank you for your help

Com.sap.portal.appintegrator.sap doesn't work

Hi all,
I needed to change the file 'WinGuiRenderLayer.properties'
I found the par under 3 locations:
d:\usr\sap\SPD\jc00\j2ee\cluster\server0\apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\portal\portalapps\com.sap.portal.appintegrator.sap
d:\usr\sap\SPD\jc00\j2ee\cluster\server0\apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\deployment\pcd
d:\usr\sap\SPD\jc00\j2ee\cluster\server0\apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\deployment\temp
I changed the file in those locations (I removed the bak extension and restarted the server).
Also, I made sure that the pars/directory contains the jar files.
After I restarted the server the application integrator iviews doesn't work (Web Dynpro, Transaction...).
Before I did the changes, I backed up the original pars/directory.
Copying the original pars didn't help.
How can I solve this?
Portal is EP6.16
Attched exception details:
Date : 10/25/2007
Time : 13:56:51:765
Message : [PortalNode.fireEventOnNode.toEventListener] event=onNodeReadyEvent, target=com.company.Orders, operation failed
[EXCEPTION]
com.sapportals.portal.prt.component.PortalComponentException: Error in init method
Component : com.sap.portal.appintegrator.sap.WebDynpro
     at com.sapportals.portal.prt.component.PortalComponentContext.init(PortalComponentContext.java:251)
     at com.sapportals.portal.prt.core.broker.PortalComponentContextItem.refresh(PortalComponentContextItem.java:267)
     at com.sapportals.portal.prt.core.broker.PortalComponentContextItem.getContext(PortalComponentContextItem.java:312)
     at com.sapportals.portal.prt.component.PortalComponentRequest.getComponentContext(PortalComponentRequest.java:385)
     at com.sapportals.portal.navigation.workAreaiView.doOnNodeReady(workAreaiView.java:238)
     at com.sapportals.portal.prt.component.AbstractPortalComponent.handleEvent(AbstractPortalComponent.java:388)
     at com.sapportals.portal.navigation.workAreaiView.handleEvent(workAreaiView.java:356)
     at com.sapportals.portal.prt.pom.ComponentNode.handleEvent(ComponentNode.java:252)
     at com.sapportals.portal.prt.pom.PortalNode.fireEventOnNode(PortalNode.java:369)
     at com.sapportals.portal.prt.pom.AbstractNode.addChildNode(AbstractNode.java:340)
     at com.sapportals.portal.pb.PageBuilder.createAndAddEmbeddediView(PageBuilder.java:178)
     at com.sapportals.portal.pb.PageBuilder.createiView(PageBuilder.java:391)
     at com.sapportals.portal.pb.PageBuilder.createAndAddiViews(PageBuilder.java:234)
     at com.sapportals.portal.pb.PageBuilder.doOnNodeReady(PageBuilder.java:576)
     at com.sapportals.portal.prt.component.AbstractPortalComponent.handleEvent(AbstractPortalComponent.java:388)
     at com.sapportals.portal.pb.PageBuilder.handleEvent(PageBuilder.java:725)
     at com.sapportals.portal.prt.component.CachablePortalComponent.handleEvent(CachablePortalComponent.java:685)
     at com.sapportals.portal.prt.pom.ComponentNode.handleEvent(ComponentNode.java:252)
     at com.sapportals.portal.prt.pom.PortalNode.fireEventOnNode(PortalNode.java:369)
     at com.sapportals.portal.prt.pom.AbstractNode.addChildNode(AbstractNode.java:340)
     at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:642)
     at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
     at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:545)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: com.sapportals.portal.prt.core.broker.PortalComponentInstantiationException: Could not instantiate implementation class com.sapportals.portal.sapapplication.SAPApplicationIntegratorComponent of Portal Component com.sap.portal.appintegrator.sap.WebDynpro because: Linkage error while loading implementation class
     at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getInstanceInternal(PortalComponentItemFacade.java:234)
     at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getComponentInstance(PortalComponentItemFacade.java:160)
     at com.sapportals.portal.prt.core.broker.PortalComponentItem.getComponentInstance(PortalComponentItem.java:732)
     at com.sapportals.portal.prt.component.PortalComponentContext.getComponent(PortalComponentContext.java:103)
     at com.sapportals.portal.prt.component.PortalComponentContext.init(PortalComponentContext.java:242)
     ... 41 more
Caused by: java.lang.NoClassDefFoundError: com/sapportals/portal/appintegrator/AbstractIntegratorComponent
Loader Info -
ClassLoader name: [com.sapportals.portal.prt.util.ApplicationClassLoader@72f155]
Parent loader name: [sap.com/com.sap.portal.appintegrator.sap]
References:
   not registered!
Resources:
   D:\usr\sap\SPD\JC00\j2ee\cluster\server0\apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\portal\portalapps\com.sap.portal.appintegrator.sap\private\classes
   D:\usr\sap\SPD\JC00\j2ee\cluster\server0\apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\portal\portalapps\com.sap.portal.appintegrator.sap\private\lib\com.sap.portal.appintegrator.sap_core.jar
The error occurred while trying to load "com.sapportals.portal.sapapplication.SAPApplicationIntegratorComponent".
     at com.sap.engine.frame.core.load.ReferencedLoader.loadClass(ReferencedLoader.java:389)
     at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
     at java.lang.Class.forName0(Native Method)
     at java.lang.Class.forName(Class.java:219)
     at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getInstanceInternal(PortalComponentItemFacade.java:228)
     ... 45 more
Severity : Warning
Category : /System/Server
Location : com.sap.portal.portal
Application : sap.com/irj
Thread : SAPEngine_Application_Thread[impl:3]_27
Datasource : 6397450:D:\usr\sap\SPD\JC00\j2ee\cluster\server0\log\defaultTrace.trc
Message ID : 000E7F3049DE005C0000002100001C4000043D4FEE02FB46
Source Name : com.sap.portal.portal
Argument Objs : com.sapportals.portal.prt.component.PortalComponentException: Error in init method
Component : com.sap.portal.appintegrator.sap.WebDynpro
     at com.sapportals.portal.prt.component.PortalComponentContext.init(PortalComponentContext.java:251)
     at com.sapportals.portal.prt.core.broker.PortalComponentContextItem.refresh(PortalComponentContextItem.java:267)
     at com.sapportals.portal.prt.core.broker.PortalComponentContextItem.getContext(PortalComponentContextItem.java:312)
     at com.sapportals.portal.prt.component.PortalComponentRequest.getComponentContext(PortalComponentRequest.java:385)
     at com.sapportals.portal.navigation.workAreaiView.doOnNodeReady(workAreaiView.java:238)
     at com.sapportals.portal.prt.component.AbstractPortalComponent.handleEvent(AbstractPortalComponent.java:388)
     at com.sapportals.portal.navigation.workAreaiView.handleEvent(workAreaiView.java:356)
     at com.sapportals.portal.prt.pom.ComponentNode.handleEvent(ComponentNode.java:252)
     at com.sapportals.portal.prt.pom.PortalNode.fireEventOnNode(PortalNode.java:369)
     at com.sapportals.portal.prt.pom.AbstractNode.addChildNode(AbstractNode.java:340)
     at com.sapportals.portal.pb.PageBuilder.createAndAddEmbeddediView(PageBuilder.java:178)
     at com.sapportals.portal.pb.PageBuilder.createiView(PageBuilder.java:391)
     at com.sapportals.portal.pb.PageBuilder.createAndAddiViews(PageBuilder.java:234)
     at com.sapportals.portal.pb.PageBuilder.doOnNodeReady(PageBuilder.java:576)
     at com.sapportals.portal.prt.component.AbstractPortalComponent.handleEvent(AbstractPortalComponent.java:388)
     at com.sapportals.portal.pb.PageBuilder.handleEvent(PageBuilder.java:725)
     at com.sapportals.portal.prt.component.CachablePortalComponent.handleEvent(CachablePortalComponent.java:685)
     at com.sapportals.portal.prt.pom.ComponentNode.handleEvent(ComponentNode.java:252)
     at com.sapportals.portal.prt.pom.PortalNode.fireEventOnNode(PortalNode.java:369)
     at com.sapportals.portal.prt.pom.AbstractNode.addChildNode(AbstractNode.java:340)
     at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:642)
     at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
     at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:545)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: com.sapportals.portal.prt.core.broker.PortalComponentInstantiationException: Could not instantiate implementation class com.sapportals.portal.sapapplication.SAPApplicationIntegratorComponent of Portal Component com.sap.portal.appintegrator.sap.WebDynpro because: Linkage error while loading implementation class
     at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getInstanceInternal(PortalComponentItemFacade.java:234)
     at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getComponentInstance(PortalComponentItemFacade.java:160)
     at com.sapportals.portal.prt.core.broker.PortalComponentItem.getComponentInstance(PortalComponentItem.java:732)
     at com.sapportals.portal.prt.component.PortalComponentContext.getComponent(PortalComponentContext.java:103)
     at com.sapportals.portal.prt.component.PortalComponentContext.init(PortalComponentContext.java:242)
     ... 41 more
Caused by: java.lang.NoClassDefFoundError: com/sapportals/portal/appintegrator/AbstractIntegratorComponent
Loader Info -
ClassLoader name: [com.sapportals.portal.prt.util.ApplicationClassLoader@72f155]
Parent loader name: [sap.com/com.sap.portal.appintegrator.sap]
References:
   not registered!
Resources:
   D:\usr\sap\SPD\JC00\j2ee\cluster\server0\apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\portal\portalapps\com.sap.portal.appintegrator.sap\private\classes
   D:\usr\sap\SPD\JC00\j2ee\cluster\server0\apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\portal\portalapps\com.sap.portal.appintegrator.sap\private\lib\com.sap.portal.appintegrator.sap_core.jar
The error occurred while trying to load "com.sapportals.portal.sapapplication.SAPApplicationIntegratorComponent".
     at com.sap.engine.frame.core.load.ReferencedLoader.loadClass(ReferencedLoader.java:389)
     at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
     at java.lang.Class.forName0(Native Method)
     at java.lang.Class.forName(Class.java:219)
     at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getInstanceInternal(PortalComponentItemFacade.java:228)
     ... 45 more
Arguments : com.sapportals.portal.prt.component.PortalComponentException: Error in init method
Component : com.sap.portal.appintegrator.sap.WebDynpro
     at com.sapportals.portal.prt.component.PortalComponentContext.init(PortalComponentContext.java:251)
     at com.sapportals.portal.prt.core.broker.PortalComponentContextItem.refresh(PortalComponentContextItem.java:267)
     at com.sapportals.portal.prt.core.broker.PortalComponentContextItem.getContext(PortalComponentContextItem.java:312)
     at com.sapportals.portal.prt.component.PortalComponentRequest.getComponentContext(PortalComponentRequest.java:385)
     at com.sapportals.portal.navigation.workAreaiView.doOnNodeReady(workAreaiView.java:238)
     at com.sapportals.portal.prt.component.AbstractPortalComponent.handleEvent(AbstractPortalComponent.java:388)
     at com.sapportals.portal.navigation.workAreaiView.handleEvent(workAreaiView.java:356)
     at com.sapportals.portal.prt.pom.ComponentNode.handleEvent(ComponentNode.java:252)
     at com.sapportals.portal.prt.pom.PortalNode.fireEventOnNode(PortalNode.java:369)
     at com.sapportals.portal.prt.pom.AbstractNode.addChildNode(AbstractNode.java:340)
     at com.sapportals.portal.pb.PageBuilder.createAndAddEmbeddediView(PageBuilder.java:178)
     at com.sapportals.portal.pb.PageBuilder.createiView(PageBuilder.java:391)
     at com.sapportals.portal.pb.PageBuilder.createAndAddiViews(PageBuilder.java:234)
     at com.sapportals.portal.pb.PageBuilder.doOnNodeReady(PageBuilder.java:576)
     at com.sapportals.portal.prt.component.AbstractPortalComponent.handleEvent(AbstractPortalComponent.java:388)
     at com.sapportals.portal.pb.PageBuilder.handleEvent(PageBuilder.java:725)
     at com.sapportals.portal.prt.component.CachablePortalComponent.handleEvent(CachablePortalComponent.java:685)
     at com.sapportals.portal.prt.pom.ComponentNode.handleEvent(ComponentNode.java:252)
     at com.sapportals.portal.prt.pom.PortalNode.fireEventOnNode(PortalNode.java:369)
     at com.sapportals.portal.prt.pom.AbstractNode.addChildNode(AbstractNode.java:340)
     at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:642)
     at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
     at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:545)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: com.sapportals.portal.prt.core.broker.PortalComponentInstantiationException: Could not instantiate implementation class com.sapportals.portal.sapapplication.SAPApplicationIntegratorComponent of Portal Component com.sap.portal.appintegrator.sap.WebDynpro because: Linkage error while loading implementation class
     at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getInstanceInternal(PortalComponentItemFacade.java:234)
     at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getComponentInstance(PortalComponentItemFacade.java:160)
     at com.sapportals.portal.prt.core.broker.PortalComponentItem.getComponentInstance(PortalComponentItem.java:732)
     at com.sapportals.portal.prt.component.PortalComponentContext.getComponent(PortalComponentContext.java:103)
     at com.sapportals.portal.prt.component.PortalComponentContext.init(PortalComponentContext.java:242)
     ... 41 more
Caused by: java.lang.NoClassDefFoundError: com/sapportals/portal/appintegrator/AbstractIntegratorComponent
Loader Info -
ClassLoader name: [com.sapportals.portal.prt.util.ApplicationClassLoader@72f155]
Parent loader name: [sap.com/com.sap.portal.appintegrator.sap]
References:
   not registered!
Resources:
   D:\usr\sap\SPD\JC00\j2ee\cluster\server0\apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\portal\portalapps\com.sap.portal.appintegrator.sap\private\classes
   D:\usr\sap\SPD\JC00\j2ee\cluster\server0\apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\portal\portalapps\com.sap.portal.appintegrator.sap\private\lib\com.sap.portal.appintegrator.sap_core.jar
The error occurred while trying to load "com.sapportals.portal.sapapplication.SAPApplicationIntegratorComponent".
     at com.sap.engine.frame.core.load.ReferencedLoader.loadClass(ReferencedLoader.java:389)
     at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
     at java.lang.Class.forName0(Native Method)
     at java.lang.Class.forName(Class.java:219)
     at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getInstanceInternal(PortalComponentItemFacade.java:228)
     ... 45 more
Dsr Component : <Server Name>
Dsr Transaction : 5a4c6ec082f111dccf17000e7f3049de
Dsr User : <User>
Indent : 0
Level : 0
Message Code :
Message Type : 1
Relatives : /System/Server
Resource Bundlename :
Session : 44
Source : com.sap.portal.portal
ThreadObject : SAPEngine_Application_Thread[impl:3]_27
Transaction :
User : <User>
Thanks,
Omri

Solved it.
This is what I did:
1) Took par from my production environment (same SP level)
2) Clear the par (by using 'Archive Remover')
3) Clear the pcd cache
4) Upload the par (redploy)\
5) Restart the portal
Thanks,
Omri

Problem Undeploying a PAR file

Hi,
Let me first give the history of this problem.
I wrote a small portal application and created a par file named RoyaltiesService.par and tried to deploy it from NWDS, but NWDS got stuck and i was not able to deploy the par file. I also realised that my portal server stopped and my efforts to start the server have gone in vain. Please see the details of that problem at <Re: Problem with protal server>
So after trying to solve the problem for few days I reformatted my machine and reinstalled the portal now. I was able to deploy other par files and everthing worked fine, but now I tried to deploy the same par file RoyaltiesService.par (the one that i tried to deploy when the problem occurred for the first time) and the same problem reoccurred i.e., my NWDS got stuck, portal server stopped and i am unable to start it. I am wondering whether my par file has something to do with this. I thought of undeploying the par file from the SDM console but i am not able to find that RoyaltiesService.par file. Then i did a search for the par file in my c:usrsap and found the following results. (File/Folder name - location)
-> RoyaltiesService - C:usrsapJ2EJC00j2eeclusterserver0appssap.comirjservlet_jspirj
ootWEB-INFportalportalapps
-> RoyaltiesService.revision - C:usrsapJ2EJC00j2eeclusterserver0appssap.comirjservlet_jspirj
ootWEB-INFportalsystem
evisions
-> RoyaltiesService.par.bak - C:usrsapJ2EJC00j2eeclusterserver0appssap.comirjservlet_jspirj
ootWEB-INFdeployment emp
-> RoyaltiesServiceapi.jar - C:usrsapJ2EJC00j2eeclusterserver0appssap.comirjservlet_jspirj
ootWEB-INFportalportalappsRoyaltiesServicelib
-> RoyaltiesServicecore.jar - C:usrsapJ2EJC00j2eeclusterserver0appssap.comirjservlet_jspirj
ootWEB-INFportalportalappsRoyaltiesServiceprivatelib
Now i want to remove this par file from the deployment. Can anyone suggest me how to do it ??
Any help will be very very helpful to me.
Thanks & Regards,
Sudhir

Hi,
You cannot remove from the file system, because the application is deployed to the PCD (Application Repository), which then replicates the application to all the cluster nodes.
You have to use the Archive Remover tool. Did you try?
Even if you cannot get the portal interface, if you can log in and create a session, you can navigate to the archive remove and remove the application.
Hope this helps.
Daniel

Document in BSEG but not in BKPF. Message displays Document not in Database

Good day!
We are using SAP 4.6C.
Our client wants to display a document posted some time ago using FB03.
The message displayed, "Document not in database. Search Document archive?"
I looked for the document in BSEG and found that the document exists there.
However, the document header data are missing in BKPF.
Is there a transaction code that could have archived/removed the data in BKPF while
not changing anything in BSEG?
Could there be a way to retrieve these data?
Thank you!

Good Day !
For your information, the pop up message prompting for archived mesages "Document is not in database. Search document archive? " is not present anymore in the release ECC 6.0. This pop existed in your release and this has been phased out as part of continuous product improvement after inputs from various customers.
In the newer releases instead of this pop up we have the message
"Document XXXX XXXXXXXXX XXXX is already archived" being displayed at the lower bottom of the screen. This helps you identify that the document was archived. This is the standard SAP behaviour.
Therefore, your document is archived. To able to retrieve this document again you can use Tcode FBL3N and change the Data source option (there is a button for that) to Archived Data.
The same you achieve in FB03 when you select Document List button and then Data Sources Button, mark the option Archive.
I hope this helps.
Best Regards,
Vanessa.

Webdynpro error in Post installation steps of SLD

Hi
We are working on EP7.0 2004s.We are using local sld.Right now I am doing the post installation steps for SLD.I added the J2EE and UME roles.In the next step I went into the administration tab of SLD for configuring.It is throwing this error.
<b>com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Exit-Plug must no be triggered with an URL when running in portal. Use portal navigation instead to navigate to another application!</b>
This is detailed exception I got.
com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Exit-Plug must no be triggered with an URL when running in portal. Use portal navigation instead to navigate to another application!
at com.sap.tc.webdynpro.progmodel.view.View.navigate(View.java:516)
at com.sap.tc.webdynpro.progmodel.view.View.navigate(View.java:462)
at com.sap.sld.wd.main.wdp.InternalMainInterfaceView.wdFirePlugToOldUI(InternalMainInterfaceView.java:154)
at com.sap.sld.wd.main.Head.onActionAdministration(Head.java:277)
at com.sap.sld.wd.main.wdp.InternalHead.wdInvokeEventHandler(InternalHead.java:227)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doHandleActionEvent(WindowPhaseModel.java:420)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:132)
at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:299)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:711)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:665)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:232)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:152)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Please help me.
Thanx & Regards,
Naresh

Hey Aviad,
Yes I did, in my case I've installed PDK SP 9 over SP2 which is prohibited. If this is your case as well do the following:
1) From the Undeployment tab of the SDM select the com.sap.pct.pdk..
components.
2) Using the Archive remover tool which can be accessed from
System Administration > Support > Portal Runtime > Administration
Console > Archive Remover --> Remove the portal applications with prefixcom.sap.pct.pdk...
3) Navigate to Content Administration > Portal content > Content
Provided by SAP > Platform Add-Ons > Developer Content
and remove all the contents below this folder.
4) Restart the server
After this you can deploy the SP9 business package using the SDM.
Hope it helps,
Roy

Using library com.sapportals.htmlb.*;

Hi,
i had created a portal aplication in the wizard. And i had joined this library (com.sapportals.htmlb.*;) to my program, meanwhile i had initialized my new form and other components of my form...such as textviews,labels, buttons and so on..
The question is, when i make the deploy in a file '.par' to the portal i can´t see the changes i had made in the components of my form...can anybody tel me why? can you give references to study implementations of this library?
Regards,
Hugo

Hi Hugo,
Assuming that you have installed the PDK for Java,
have you tried cleaning the par file and re-deploying?
This is done via: Java Development>Development>Component Manager>Archive Remover> From here select your particular project and hit clean. This removes the old code entirely from the system and you can redeploy with satisfaction that the old code will not be referenced.
Regards
Daniel

Archive removed

Similar Messages

Maybe you are looking for