Profile consistency check when operation mode change

If the number of work processes in the profiles is changed, the system can no longer switch operation modes until after a restart of the instance. It's therefore necessary to adjust the configuration of the operation modes after a change to the profiles.
In above paragraph, I don't understand why the system can not switch mode if the number of wp in profile is changed? Does system will compare wp number in profile with currently running wp number before the operation mode switch? Please advise.
Thanks.
James

Yes, I can understand it, when the number of work processes is changed, we need redefine the operation mode.
But I am confused this sentence "If the number of work processes in the profiles is changed, the system can no longer switch operation modes until after a restart of the instance. "
After the number of work processes in profile is changed, I think it will not impact instance immediately until restart the instance. According to this sentence, it seems when I change the parameter in profile, it impacts the instance immediately and the system can not switch operation mode right now if we don't restart the instance. Is it reasonable? And I think the operation mode still need redefine even if we restart the instance, since scenario in Ralph's description. Is my thought right?
Thanks so much.
James

Similar Messages

APO DP Forecast profile consistency check

I am using APO DP V5.
Has anyone any experience of using the 'forecast profile consistency check' pgm /sapapo/rmdp_fcst_prpfl_consis?
What exactly does it do?
Thanks,
Bob Austin, Atos Origin

Hello,
This report /SAPAPO/RMDP_FCST_PRPFL_CONSIS is consistency for forecast profiles
While there is no need to schedule the report automatically at regular intervals, there are some special situations in which it can be very useful.
When must this report be run?
1. When you transport forecast profiles from a system A to a system B. In this case, you must convert the internal version indicator (Id).
2. If you are having problems with the date display or if the system changes from the relative date specification to the absolute specification for no obvious reason.
When should you run this report?
1. If you are working with generated forecast profiles (user parameter /SAPAPO/FCST_GUIDS).
2. If you are using a manual forecast.
What exactly does this report do?
1. The internal version ID is checked.
2. Date fields are checked. Fields filled with 00000000 are initialized.
3. Overall profiles without any single profiles are deleted.
4. Generated forecast profiles that are no longer assigned to a selection are deleted.
5. The assignment of forecast profiles to a selection is deleted if the forecast profile no longer exists.
6. Parameters for the manual forecast are deleted for any forecast profiles that no longer exist.
Source of above details : Note 558995 - Advice on consistency report for forecast profiles

Logs for 'Operating mode' change in mirroring

Logs for 'Operating mode' change in mirroring
Hi Everyone,
Is there any log,that shows when the Operating mode of a database involved in mirroring(SQL SERVER 2008 R2) has been changed from asynchronous to synchrous(or vise versa).
Regards,
Aspet
A.G

Try looking into trace log files
DECLARE @filename VARCHAR(100), @filenum int
SELECT @filename = CAST(value AS VARCHAR(100))
FROM fn_trace_getinfo(DEFAULT)
WHERE property = 2
AND traceid = 1
AND value IS NOT NULL
SELECT @filename
SELECT @filename = substring(@filename, 0, charindex('_', @filename)+1) + convert(varchar, (convert(int, substring(left(@filename, len(@filename)-4), charindex('_', @filename)+1, len(@filename)))-4)) + '.trc'
SELECT @filename
SELECT gt.EventClass,
te.Name AS EventName,
gt.TEXTData,
gt.NTUserName,
gt.NTDomainName,
gt.HostName,
gt.ApplicationName,
gt.LoginName,
gt.SPID,
gt.StartTime,
gt.EndTime,
gt.ObjectName,
gt.DatabaseName,
gt.FileName
FROM [fn_trace_gettable](@fileName, DEFAULT) gt
JOIN sys.trace_events te ON gt.EventClass = te.trace_event_id
WHERE EventClass = 116
AND TEXTData LIKE '%Alter
database%'
ORDER BY StartTime;
Best Regards,Uri Dimant SQL Server MVP,
http://sqlblog.com/blogs/uri_dimant/
MS SQL optimization: MS SQL Development and Optimization
MS SQL Blog:
Large scale of database and data cleansing
Remote DBA Services:
Improves MS SQL Database Performance

LiveCache Consistency Check question, OM17

I have a general question about a LiveCache Consistency Check (transaction OM17). I know that it is a data inconsistency b/w the SAP APO database and SAP APO LiveCache. But what does that mean to a functional user? Can someone explain this in layman's terms?

In Layman terms, you can say that this checks the INCONSISTENCY between LiveCache and Database.
Here is a detailed documentation on each of the Object Types
Consistency Check for Setup Matrices
The consistency check for setup matrices contains:
· A check whether the setup matrices exist in liveCache
· A check whether the setup transitions exist in liveCache
· A field comparison between the setup transitions in the database and those in liveCache
When the setup matrices are corrected, the setup matrices in liveCache are completely generated from those in the database. Previously nonexistent setup matrices and setup transitions are newly created in liveCache. Superfluous setup transitions are deleted from liveCache. Setup transitions that differ at the field level are adjusted to match the database status.
Consistency Comparison for Block Basis Definitions
Use
When you set this indicator, checks are performed in liveCache and in the database on characteristic values for block basis definitions:
· The existence of block basis definitions is checked.
· The consistency of the characteristic values is checked.
After the checks you can call a correction function in the check results display. When correcting the error, the system deletes obsolete block basis definitions in liveCache. The system completes or corrects missing or inconsistent block basis definitions in liveCache.
Note
The check is performed independently of the planning version.
Consistency Check for Resources
The consistency check for resources contains:
· A check that the resource and corresponding time stream exist in liveCache
· An check that a resource's characteristic blocks exist in liveCache
· A field comparison between the database resource and the liveCache resource
When correcting the resources, the resources in liveCache are completely generated from the database resources. Previously nonexistent resources are created in liveCache.
Consistency check for downtimes caused by maintenance order
The consistency check for maintenance downtimes contains:
A check that the maintenance downtime has a reference to an existing maintenance order.
A check that the dates of maintenance downtime correspond to the exisiting maintenance order.
When correcting the maintenance downtime errors, downtimes without maintenance order are deleted and wrong dates of downtimes are corrected in relation to the maintenance order.
Consistency Check for Product Location Combinations
Use
If you set this indicator the system executes a consistency check for product location combinations. The consistency check for product location combinations includes:
· A check for the existence of a product location combination in the database and in liveCache
· A field comparison between product location combinations in the database and in liveCache
· The determination of obsolete entries for product location combinations in the database
· A check for the existence of characteristic value assignments for product location combinations in the database and in liveCache
· A field comparison of characteristic value assignments for product location combinations in the database and in liveCache
After the check you can call a correction function from the display of check results. For the correction, the system deletes obsolete product location combinations from the database and in liveCache. The system corrects inconsistent product location combinations and characteristic value assignments for product location combinations in liveCache.
Consistency Check for Stocks
Use
If you set this indicator the system executes a consistency check for stocks. The consistency check for stocks includes:
· A check for the existence of a stock in the database and in liveCache
· A field comparison between stocks in the database and in liveCache
· The determination of obsolete entries for stocks in the database
· A check for the existence of characteristic value assignments in the database and in liveCache
· A field comparison between characteristic value assignments for batch stocks in the database and in liveCache
After the check, you can call a correction function from the display of check results. For the correction, the system attempts to correct inconsistent stocks in the database and in liveCache. If a correction is not possible, the stocks are deleted in the database and in liveCache. The system corrects characteristic value assignments for batch stocks in liveCache.
After inconsistent stocks have been corrected, it may be necessary to start the delta report in order to reconcile SAP APO and SAP R/3.
Consistency Comparison of Configuration/CDP for Orders
Use
When you set this indicator, the system performs a consistency check with regard to configuration or CDP (characteristic value assignments/ requirements) for receipts/requirements belonging to orders:
· In the case of products with variant configuration and product variants, the system checks whether there is a referenced configuration in the database.
· In the case of products with CDP, the system checks whether CDP characteristics exist.
Note
In the area Restrictions, you can use the indicator CDP: Detailed Check to define a detailed check for CDP characteristics. If you set this indicator, the CDP data used for the orders is also compared with the product master.
· For products without configuration/CDP, the system checks whether invalid references to variant configuration or invalid CDP characteristics data exist.
After the check, you can call a correction function in the check results display. When executing the correction, the system tries to adjust inconsistent orders in liveCache.
After inconsistent orders have been corrected, you may need to start the delta report to compare the SAP R/3 system and SAP APO again.
Dependencies
The consistency check for configuration or CDP data is very time-consuming. You should therefore limit the comparison as far as possible to certain products or locations.
Consistency Check for Production Campaigns
If orders are assigned to production campaigns that do not exist in the database, this leads to inconsistent campaigns.
You can correct inconsistent production campaigns by removing all orders from them. That means that the campaign assignments are removed from the orders in liveCache.
Consistency Check for Operations
In the database table of /SAPAPO/OPR operations, there may exist operations that have no orders in liveCache, no orders for a simulation version, orders for deleted simulation versions, or no external operation number. These operations place an unnecessary load on the database table and can hinder system performance.
Consistency Check for Planning Matrices
As planning matrices are not master data, they are only located in liveCache. For each production version, there is a record in the database with information about matrices that must exist for this production version and whether the last matrix explosion was successful.
The consistency check for planning matrices checks:
· Whether the matrices associated with each record on the database exist in liveCache
· Whether the records associated with all the matrices in liveCache exist on the database
· Whether the last matrix explosion was successful.
If inconsistencies are discovered, they can be corrected. As corrections are made by recalculating the inconsistent matrices, the process can take a while and should only be done for large matrices (with many orders or many item variants) at times when it can be guaranteed not to hinder any other system processes.
Consistency Check for Simulation Versions
This is a check for whether simulation versions exist in liveCache.
Correction does not take place automatically. Simulation versions that still exist in the database but no longer exist in liveCache do not influence the running of the system. If necessary, they can be deleted using transaction /SAPAPO/CDPSS0.
Consistency Check for Product Allocations
The consistency check for product allocations checks the data for product allocation assignment from the database and compares this with the incoming orders quantity in Demand Planning. Surpluses or shortages are displayed and can be corrected.
The reconcile is only executed for product allocation groups with a direct connection to the product allocation group in the planning area if the connection is also fully defined.
There may be long runtimes during the consistency check due to the data structure. The following factors can hinder performance:
· Number of characteristics combinations
· Number of periods in a time series
· Number of sales orders that take product allocations from a time stream
Error in the reconcile
If it is not possible to reconcile the incoming orders quantity, the data records are issued again with a relevant error message. Check the following causes and attempt again.
Check:
· If the planning area to be checked is locked
· If the time streams are initialized (after liveCache has been initialized)
· If all characteristics combinations area available in the planning area
· The wildcard indicator for collective product allocation
· The settings for your planning area
Due Delivery Schedules/Confirmations Consistency Check
When a scheduling agreement release is received from a customer for sales and distribution scheduling agreement items, a due delivery schedule is created and stored in liveCache. As soon as a confirmation for a due delivery schedule containing at least one schedule line with a quantity larger than zero is generated, an object is also created for it in liveCache. The transaction data for sales and distribution scheduling agreement items contains, amongst other things, an entry with the key of the due delivery schedule object currently located in liveCache and an entry with the key of the confirmation that is currently valid in the database. During the check, the system checks whether liveCache objects exist for sales and distribution scheduling agreement items and whether the transaction data entries are correct.
The following individual checks are made for active sales and distribution scheduling agreement items:
· Is there an operative scheduling agreement release and/or forecast/planning delivery schedule in the database, but no associated liveCache object?
· Is there a confirmation in the database, but no associated liveCache object?
· Is there a due delivery schedule in liveCache, without at least one existing operative scheduling agreement release and/or forecast/planning delivery schedule?
· Is there a confirmation in liveCache, without an existing confirmation in the database?
· Is the key in the transaction data in the database that shows the current due delivery schedule in liveCache, also that of the actual liveCache object?
· Is there actually a confirmation in the database for the key in the transaction data that shows the currently valid confirmation in the database?
If a sales and distribution scheduling agreement item is inactive, there are not allowed to be any due delivery schedules or confirmations in liveCache. In this case, the following checks are made:
· Is there a due delivery schedule in liveCache for an inactive sales and distribution scheduling agreement item?
· Is there a confirmation in liveCache for an inactive sales and distribution scheduling agreement item?
Consistency Check for Production Backflushes
Partially confirmed orders cannot be deleted from liveCache. For each partially confirmed order of the database table, there must be a corresponding order in liveCache. If no order exists, there is a data inconsistency that can only be rectified by deleting the order from the database tables of the confirmation.
Entries for orders that have already been confirmed exist in the status matrix. The entry in an order's status matrix is deleted when the confirmed order is deleted by the /SAPAPO/PPC_ORD archiving report. Each status matrix entry for which database tables of the confirmation do not exist, present an inconsistency that can only be removed by deleting the status matrix entry.
Consistency Check for iPPE Objects
The iPPE object is not an iPPE master data structure. It is a data extract that is generated for each iPPE access object.
The consistency check for the object checks that it exists in liveCache and also determines its identity using the backup copy in the database. When correcting the object, the copy from the database is written to liveCache.
It is necessary to check the object if the following error message occurs: 'Error while calling COM routines via application program' (/sapapo/om 102) with return code 1601, 1602, or 1603. This does not apply to liveCache initialization.
Consistency Check for Procurement Scheduling Agreement Items
The following three objects represent procurement scheduling agreement items (scheduling agreement in short):
1. Scheduling agreement schedule lines
2. Release schedule lines
3. Confirmations
All these objects are located in liveCache. Release schedule lines and confirmations are also located in the database with a historical record. Depending on the process that was set up for the scheduling agreement, not all objects exist in liveCache or have historical records.
If goods movements exist for an object, there must always be at least one entry in liveCache. If all schedule lines are covered by goods receipts, at least one schedule line will exist in liveCache with the number '0000000000' and an open quantity of 0.
A liveCache crash, operator errors, and program errors can all cause inconsistencies. Below is a list of all the inconsistent statuses that have been identified and that can be removed:
1. The object is not in liveCache but goods receipts exist.
2. The number of input nodes and output nodes is different.
3. There are no input nodes at the order, but the material exists in the source location for the order.
4. The original quantity at the source of an order is different from that at the destination.
5. The accumulated quantities in liveCache are different from those in the database (the cumulative received quantity, for example).
6. The set process is compared with the status in liveCache.
7. A check is made to see whether the scheduling agreement is being planned in APO or in R/3 and whether the schedule lines have the appropriate specification.
If a schedule line inconsistency is identified, no more checks for inconsistencies are made, instead it moves on to the next schedule line.
Consistency Check for MSP Orders
Provides a list of maintenance and slot orders that
·     Exist in the database but have no corresponding orders in the liveCache
·     Exist in the liveCache, but have no corresponding orders in the database
Procedure
From within the list, you can either
·     Correct the inconsistencies
If you choose to do this, the system deletes the selected orders from the database and/or liveCache.
You receive a message that the selected order(s) have been deleted.
·     Leave the inconsistencies in the database and/or liveCache
Such inconsistencies place an unnecessary load on the database and/or liveCache. Moreover, those orders that exist in the liveCache, but have no corresponding orders in the database, influence the scheduling results of subsequent orders in the liveCache
Hope this helps
Regards
Kumar Ayyagari

DPM 2012 R2 Consistency Check (Replica Inconsistent) Error for Failover Cluster

I have a SCDPM 2012 R2 instance running against a Windows Server 2012 R2 Failover Cluster on the network.
However, any new/migrated Roles/Virtual machines that I add under an existing protection group always gives me an error saying that the replica is inconsistent.
I've verified the following :
1. All windows updates are applied on the cluster hosts & the DPM server.
2. The VSS and DPMRA services are running on the hosts & DPM server.
3. The Windows Server Backup feature has been installed on all the machines as well.
4. The short term storage disks attached to the DPM server are LUNs and there is enough free space on those.
What else am I missing that could be causing the Replica to be inconsistent - considering that these are new VMs on the hosts themselves - is there a way to force a fresh replica to be created?

Do not remove any of the providers they come with the system. There is just something wrong with that VM, your trying to backup, as it could take the initial replica creation.
Check all of the following
1) Make sure you have enough C drive space on the guest - need space to create a snapshot
2) Check the vssadmin list wirters for any errors
If none of the above, rerun the consistency check when no other backup is running. Check the Application log on the host for any vss failures
Ensure you have all the DPM hotfixes - I am compiling a list since i've been thru many DPM issues.
Great product when you get it going but like any product there are bumps in the road :)
ANNCEX

SAP Note 23345 for Oracle Consistency Check

Dear All,
I would like to run a Consistency check using backup type = online option via DB VERIFY but unfortunately each time I run the backup online using the below commands I am getting permission error.I have run the commands below using ORA<SIDADM>
brbackup -u / -m all -w only_rmv -e <parallel degree> -c
brbackup -u / -m all only_dbv -c -t online -e 3
brbackup -u / -m all -w only_dbv -e 3 -c
brbackup -u / -c force -w only_dbv -t online -p init<sidadm>.sap -m ALL -e 3
brbackup -u / -c force -w only_dbv -p init<sidadm>.sap -m ALL
I hope someone could provide what is the best command to use in order to execute the Consistency check in Online mode as I am planning to schedule it on weekly basis with the Online option..
Thank you.
Regards,
John

Do not double post the same question in different forums:
SAP Note 23345 for Oracle Consistency Check
Markus

When in mode dev to develop my website, I can't open buttons and PDF files to check my changes or somebody else's changes. What is wrong ? (I updated Adobe Reader)

when in mode dev to develop my website, I can't open buttons and PDF files to check my changes or somebody else's changes. What is wrong ? (I already updated Adobe Reader)

Oh no... NOT THE 99-PAGER!!! Anything but THAT!!!

When do consistency check for a sharepoint content databse : that RBSID in table AllDocStreams registered with RBS is invalid

Hi
In my sharepont farm a web application configured with RBS and its working fine,
when users upload pdfs the no of files are increased in RBS file system folder,
but when i run Consistency check before running RBS maintainer for cleaning garbage dta for this web applications content database , i faced below issue , its saying
C:\Program Files\Microsoft SQL Remote Blob Storage 10.50\Maintainer>Microsoft.Da
ta.SqlRemoteBlobs.Maintainer.exe -ConnectionStringName RBS_2 -Operation Consiste
ncyCheck -ConsistencyCheckMode c
Starting Maintainer tasks.
Starting RBS consistency check with check only.
The column <RbsId> in table <dbo.AllDocStreams>
registered with RBS is invalid.
and also when i repair consistency checks its saying same message, that RBSID in table AllDocStreams registered with RBS is invalid.
and also its recommended to check consistency before cleaning garbage data from content database
adil

http://social.technet.microsoft.com/Forums/sharepoint/en-US/e9bda580-b9e7-48c5-b18c-485e016677a1/rbs-maintainer-not-cleanup-files-in-file-system-sharepoint-2010?forum=sharepointadminprevious
The GC of RBS maintainer just purges BLOBs in SQL Server. And FILESTREAM GC is needed to purge the files in file system.
http://www.sqlskills.com/BLOGS/PAUL/post/FILESTREAM-garbage-collection.aspx : (FILESTREAM GC)... runs as part of the database checkpoint
process. This is what causes some confusion - an old FILESTREAM file will not be removed until after it is no longer needed AND a checkpoint runs.
Yes, In Simple recovery mode, just run SQL statement:
CHECKPOINT;
In Full recovery mode, two transaction log with CHECKPOINT are needed. Detail in the link above.
http://blog.avtex.com/2011/05/16/remote-blob-store-rbs-and-sharepoint-2010-part-2/
If this helped you resolve your issue, please mark it Answered

Is Normal? Consistency Check is cancelled when File is Restored

Is it normal operation for an on-going Consistency Check to be canceled by the system when a file restore is performed on the same volume?
This happens in my environment, however I haven't found any documentation supporting it.

Synchronization jobs are definitely canceled during a restore, so it would not surprise me at all that a consistency check would also be canceled. You can get around this by restoring the data to another location (perhaps the DPM server itself) and then
manually copying the data to the target server. More work, I know, but it will not interrupt a consistency check.

How to change the 'Default operating mode' of a mapping on the repository and not from the client

Hi everybody,
I am using OWB 11.2.0.3 and under the mapping's configuration property, I have the necessity to change the Run time parameter "Default operating mode" to SET_BASED in almost all my mappings.
Because I have 745 mappings in which the Default operating mode is different from SET_BASED, instead to open 745 times the 'Configure' and update manually the value, is there a way to update safely these values (with an oracle predefined script) directly on the repository ?
I know that exists a view called CMPSTRINGPROPERTYVALUE_V based on a table called CMPSCOPrpClasses, but changing this table it's very complicated for me because contains only keys and then I don't know in which way is connected with all the other structures....
If somebody knows a method more efficient to do these updates on the repository and not from OWB client I will appreciated it!
Thanks in advance
Alessandro

Urgent... help!!! Thanks
in short, my server log says transaction access mode is "read only", so my calling home.create() always triggers a transaction rollback. How to change the access mode to "read write"?
Is possible to work out through one of the descriptor files? Or ini settings of the underlying pointbase database? Or any other way around?

Unable to change the operating mode in informatica admin tool.

hi
i have installed Informatica 8.6.0
my repository service is running . and i have also created the integration service but its not running, the reason as i fount out in various blogs is that my repository is iin exclusive mode .
so , i tried to change it to normal mode . but the problem is as i select normal in the drop-down list in general properties operating mode option and click ok , nothing's happening a and the page error is coming as shown below:
Can't move focus to the control because it is invisible ,not enabled or of a type that does not accept the focus
Is this an error of internet explorer ??? i am using IE 7.or are there any options that i need to enable???
what should i do in this case???
plz help !!!!
Edited by: Nikhil.S on Jun 8, 2011 3:37 AM
Edited by: Nikhil.S on Jun 8, 2011 3:41 AM

I got the same error and after I tested with firefox and everything.. I found out the issue (in my case):
- Under Database properties, The value for "ConnectString" property contains a space at the end.
-Example "host.oracle.com "
- Solution: I remove the space at the end , save it, and Now I can modify the operatingmode to Exclusive
Edited by: hcamacho on Jun 24, 2011 1:53 PM

When connect appletv to tv it is asking to check the resolution and change the resolution

First time when I am connecting appletv to SamsungTV it is asking to check the resolution and change the resolution.

Keynote can not burn DVD discs, nor can it compile a video DVD project
If you have iDVD installed on your Mac, You can export the Keynote presentation to iDVD to create a video DVD:
from within Keynote: Share > Send to > iDVD

TS3999 when I click on my iCloud panel, Calendars, I get an error message that says, Setup can't continue because Outlook isn't configured t have a default profile. Check you Outlook settings and try again." How do I set up these settings in Outlook 200

when I click on my iCloud panel, Calendars, I get an error message that says, Setup can't continue because Outlook isn't configured t have a default profile. Check you Outlook settings and try again." How do I set up these settings in Outlook 2007

Here are two threads you may want to review. I'm sure there are others. Good luck!
https://discussions.apple.com/thread/3427840?start=0&tstart=0
http://www.slipstick.com/outlook/icloud-outlook-problems-syncing-calendar/

TS1424 apple store,just wanted to check on how to change my area settings in itunes from United States to United Arab Emirates(that's where i stay).it got changed when i tried to download google maps from the US store in itunes.please help me out here.Tha

Apple store,just wanted to check on how to change my area settings in itunes from United States to United Arab Emirates(that's where i stay).it got changed when i tried to download google maps from the US store in itunes.please help me out here.Thanks

Please please help me, if you know how.

Stroke profile is deleted when brush style is changed. Why, and can I prevent this from happening?

I have several brush styles that I routinely distort with custom stroke profiles. Unfortunetly, every time I change the brush style, the profile is lost. Can I prevent this from happening?

Scott, thanks for responding.
I've done that but there are too many variations to create a Graphic Style for everyone possible combination. Interestingly, the profile is not lost when switching to the "Basic" brush appearance, only when switching to an art or pattern brush. And even more frustrating is that the "Edit Profile" tool does not work properly with art or pattern brushes. When the profile is edited the points do not remain positioned properly. This means a profile must be edited on a "basic" stroke, saved, then assigned to the "art brush" stroked. It's crazy. And the interface for saving and assigning profiles is antiquated, to say the least. You cannot even overwrite a profile!
The "Pressure" option is somewhat useful, in place of editing a profile, but I think the inability to effectively edit a profile on an artbrush is a bug in AI.

Profile consistency check when operation mode change

Similar Messages

Maybe you are looking for