System Maintenance Procedures

This has come up - I want to see what others do to'maintain' their systems
I run this: http://www.maintain.se/cocktail once a week (pilot run the standard crons and cache cleaning... etc..)
Then once a month I run Disk Warrior and Tech Tool
I've been doing this for 'literally' years... well rephrase
after earlier faillings, went to tech tool after some of their early blunders (bugs) switched to disk warrior then added cocktail
SO...
In a professional audio situation of intensive hard drive use (I have over a terbyte in storage on four drives)
Looking for the definite answer:
How Do You Maintain OS X?

Tried a PRAM reset yet?
Resetting your Mac's PRAM and NVRAM
http://docs.info.apple.com/article.html?artnum=2238

Similar Messages

Automated system maintenance timing

iMac early 2008, 2GB RAM, 2.8GHz processor, HD 320 GB total, 225GB available, OS 10.6.8
Whilst researching various causes for a Mac running slowly, I came across the statement that automated system maintenance procedures are scheduled by default to occur in "the early morning" hours, provided that the computer is running 24/7. If I were to leave my computer on, it would go into sleep mode, as would I, during these early morning hours (assuming this to mean 1am etc.). Do the automated processes indeed occur in the 1am range and if so, will they happen if the computer is in sleep mode?

Sorry that you feel that precision is not required in dealing with a modern
operating system, and that the obsolete answer appears to fit your ideas
on how to maintain a Mavericks system when compared to an older one.
On more than one occasion, advice has been suggested without bearing.
So be it with your interest in getting an answer that fits Mavericks 10.9
since the factors that did change for this new system, are not addressed
by the reply you sought to include as a correct response.
And, I also gave you a bonus tip on a historically correct (to Mavericks)
source of content that can be used with Mavericks for issues of a slow mac.
Too bad I wasted some time and research, on your behalf. If I weren't
working for free, I'd bill you double, and offer you to try a retail product.
Your understanding of an answer has not been helpful to a resolution.
However it does appear you did not read the link that supports my point:
This is current to Mavericks, cited by Pondini as of now:
On Snow Leopard 10.6.x and Later, if your Mac is powered-on but sleeping
during those hours, the scripts will run shortly after it awakes.
If you do not want current information on OS X 10.9.5, why ask and
accept info that was OK prior to Lion 10.7.5 & think that's current??
Is english your first language? I can try google translate if it helps...
Good luck and happy computing!

Scheduled system maintenance on US data center - November 23rd 2014

To ensure the highest levels of performance and reliability, we've scheduled a database server upgrade on our US data center. To minimize the customer impact, the upgrade is scheduled at the most convenient hours and will take up to 8 hours to complete. During the maintenance procedure, creating and updating content, Partner registration, trial site creation, publish from Muse, sFTP, APIs and some site admin sections will not be available. Additionally, during the 8 hours maintenance procedure, all sites on the US data center will experience 4 sessions of 15 minutes downtime. Except for the 4 scheduled downtime sessions, the website front-ends will not be impacted by the maintenance.
Maintenance schedule:
Start date and time: Sunday, November 23rd, 3:00 AM EST (check data center times)
Duration: We are targeting a 8 hours maintenance window
Customer impact:
Partner registration, Trial site creation, Adobe Muse publish, APIs, FTP and some admin section will not be available through the entire maintenance window on all data centers
All websites and services on US data center will experience 4 sessions of 15 minutes downtime sometimes within the maintenance window
Creating or updating content on sites located on US data center will be unavailable during the maintenance procedure
For up to date information about system status, check the Business Catalyst System Status page. We apologize for any inconvenience caused by these service interruptions. Please make sure that your customers and team members are made aware of these important updates.
Thank you for your understanding and support,
The Adobe Business Catalyst Team

agents will be online for update from console.
Method 1: Update the protection agents from the Data Protection Manager Administrator Console
Open the Data Protection Manager Administrator Console.
Click the Management tab, and then click the
Agents tab.
In the Protected Computer
list, select a computer, and then click Update on the Action pane.
Click Yes, and then click
Update Agents.
Note You may have to restart the computer after you install the agent upgrades.
Method 2:Update the protection agents on the protected computers
Obtain the update protection agent package from the following directory on the System Center 2012 R2 Data Protection Manager server:
<var>Data_Protection_Manager_installation_location</var>\DPM\DPM\Agents\RA\4.2.1217.0
The installation packages are as follows:
For x86-based updates: i386\1033\DPMAgentInstaller_KB2904687.exe
For x64-based updates: amd64\1033\DPMAgentInstaller_kb2904687_AMD64.exe
Run the appropriate DPMAgentInstaller.exe package on each protected computer, based on the architecture of the agent.
Open the Data Protection Manager Administrator Console on the System Center 2012 R2 Data Protection Manager server.
Click the Management tab, and then click the
Agents tab. Select the protected computers, update the information, and then verify that the agent version number is 4.2.1217.0
Have a nice day !!!

Scheduled system maintenance on EU data center - October 26th, 2014

To ensure the highest levels of performance and reliability, we've scheduled a database server upgrade on our EU data center. To minimize the customer impact, the upgrade is scheduled at the most convenient hours and will take up to 6 hours to complete. During the maintenance procedure, creating and updating content, Partner registration, trial site creation, publish from Muse, sFTP, APIs and some site admin sections will not be available. Additionally, all sites on the EU data center will experience a 20 minutes downtime sometimes during the maintenance window. Except for the scheduled 20 minutes downtime, the website front-ends will not be impacted by the maintenance.
Maintenance schedule:
Start date and time: Sunday, October 26th, 9:00 AM UTC (check data center times)
Duration: We are targeting a 6 hours maintenance window
Customer impact:
Partner registration, Trial site creation Muse Publish, APIs, FTP and some admin section will not be available through the entire maintenance window on all data centers
All websites and services on EU data center will experience a 20 minutes downtime sometimes within the maintenance window
Creating or updating content on sites located on EU data center will be unavailable during the maintenance procedure
For up to date information about system status, check the Business Catalyst System Status page. We apologize for any inconvenience caused by these service interruptions. Please make sure that your customers and team members are made aware of these important updates.
Thank you for your understanding and support,
The Adobe Business Catalyst Team

Congrats to Alan! Only one article, but it's a good one!
System Center Technical Guru - October 2014
Alan do Nascimento Carlos
ALM and IT Operations - Management 360 with System Center Operations Manager
in 06 Steps
Ed Price: "Lots of images. Great job breaking up the steps! Could benefit from a TOC and References. Great article!"
GO: "Thanks for the only article. great btw. :-)"
Ed Price, Azure & Power BI Customer Program Manager (Blog,
Small Basic,
Wiki Ninjas,
Wiki)
Answer an interesting question?
Create a wiki article about it!

Scheduled system maintenance on US data center - March 15th 2015

To ensure the highest levels of performance and reliability, we've scheduled a database server upgrade on our US data center. To minimize the customer impact, the upgrade is scheduled at the most convenient hours for the region and will take up to 6 hours to complete. During the maintenance procedure, Partner registration, trial site creation, publish from Muse, sFTP, APIs and some site admin sections will not be available for sites on all data centers (including EU and AU). Additionally, during the 6 hours maintenance procedure, all sites on the US data center will experience 2 sessions of 1 minute downtime. Except for the 2 scheduled downtime sessions, the website front-ends will not be impacted by the maintenance.
Maintenance schedule:
Start date and time: Sunday, March 15th, 6:00 AM UTC (check data center times)
Duration: We are targeting a 6 hours maintenance window
Customer impact:
Partner registration, Trial site creation, Adobe Muse publish, APIs, FTP and some admin sections will not be available through the entire maintenance window on all data centers
All websites and services on US data center will experience 2 sessions of 1 minute downtime sometimes within the maintenance window
For up to date information about system status, check the Business Catalyst System Status page. We apologize for any inconvenience caused by these service interruptions. Please make sure that your customers and team members are made aware of these important updates.
Thank you for your understanding and support,
The Adobe Business Catalyst Team

Congrats to Noah and Mr. X!
System Center Technical Guru - March 2015
Noah Stahl
Make System Center Orchestrator Text Faster than a Teenager using PowerShell
and Twilio
Ed Price: "Wow, I love the breakdown of sections. As Alan wrote in the comments, "Wow! Great article!""
Mr X
How to educate your users to regularly reboot their Windows computers
Ed Price: "I love the table and use of code snippets and images! Great article!"
Ed Price, Azure & Power BI Customer Program Manager (Blog,
Small Basic,
Wiki Ninjas,
Wiki)
Answer an interesting question?
Create a wiki article about it!

Scheduled system maintenance on AU and EU data centers - March 8th 2015

To ensure the highest levels of performance and reliability, we've scheduled a database server upgrade on our AU and EU data centers. To minimize the customer impact, the upgrade is scheduled at the most convenient hours for the regions and will take up to 6 hours to complete. During the maintenance procedure, Partner registration, trial site creation, publish from Muse, sFTP, APIs and some site admin sections will not be available for sites on all data centers (including US). Additionally, during the 6 hours maintenance procedure, all sites on the AU and EU data centers will experience 2 sessions of 1 minute downtime. Except for the 2 scheduled downtime sessions, the website front-ends will not be impacted by the maintenance.
Maintenance schedule:
Start date and time: Sunday, March 8th, 6:00 AM UTC (check data center times)
Duration: We are targeting a 6 hours maintenance window
Customer impact:
Partner registration, Trial site creation, Adobe Muse publish, APIs, FTP and some admin sections will not be available through the entire maintenance window on all data centers
All websites and services on AU and EU data centers will experience 2 sessions of 1 minute downtime sometimes within the maintenance window
For up to date information about system status, check the Business Catalyst System Status page. We apologize for any inconvenience caused by these service interruptions. Please make sure that your customers and team members are made aware of these important updates.
Thank you for your understanding and support,
The Adobe Business Catalyst Team

Congrats to Noah and Mr. X!
System Center Technical Guru - March 2015
Noah Stahl
Make System Center Orchestrator Text Faster than a Teenager using PowerShell
and Twilio
Ed Price: "Wow, I love the breakdown of sections. As Alan wrote in the comments, "Wow! Great article!""
Mr X
How to educate your users to regularly reboot their Windows computers
Ed Price: "I love the table and use of code snippets and images! Great article!"
Ed Price, Azure & Power BI Customer Program Manager (Blog,
Small Basic,
Wiki Ninjas,
Wiki)
Answer an interesting question?
Create a wiki article about it!

Getting error while opening layout in mobile system maintenance

Hi Experts,
I implemented note 904571 to prefilldata, with which all standard layouts loaded to mobile system maintenance. But problem here is if I try to open any one of the layout its giving following error
"An unhandled exception has occured in your application. If you click continue, the application will ignore this error and attempt to ccontinue. If you click Quit, the application will be shut down immediately.
Object variable or with variable not set."
If I click on details of error, its giving following details
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
Exception Text **************
System.NullReferenceException: Object variable or With block variable not set.
   at Microsoft.VisualBasic.CompilerServices.LateBinding.LateGet(Object o, Type objType, String name, Object[] args, String[] paramnames, Boolean[] CopyBack)
   at MSY.Tlayoutdet1.ctrlctrlbtnOpen_onClicked() in C:\Ars_Translation50\Batch\app\MSY\src\Tlayoutdet1.vb:line 281
   at SAP.MT.FW.UI.ExposedFWElements.CoreCtrlButton.BtnClicked()
   at SAP.MT.FW.UI.ExposedFWElements.CoreCtrlButton.IPeerCtrlListener_btnClicked()
   at SAP.MT.FW.UI.PeerLayer.PeerCtrlButton.button_Click(Object sender, EventArgs e)
   at System.Windows.Forms.Control.OnClick(EventArgs e)
   at SAP.MT.FW.UI.NativeControl.NBaseControl.OnClick(EventArgs e)
   at SAP.MT.FW.UI.NativeControl.NButton.OnClick(EventArgs e)
   at SAP.MT.FW.UI.NativeControl.NButton.mButton_Click(Object sender, EventArgs e)
   at System.Windows.Forms.Control.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ButtonBase.WndProc(Message& m)
   at System.Windows.Forms.Button.WndProc(Message& m)
   at System.Windows.Forms.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
Loaded Assemblies **************
mscorlib
    Assembly Version: 1.0.5000.0
    Win32 Version: 1.1.4322.2407
    CodeBase: file:///c:/windows/microsoft.net/framework/v1.1.4322/mscorlib.dll
MobileClient
    Assembly Version: 5.0.0.0
    Win32 Version: 5.11.0.40
    CodeBase: file:///C:/Program%20Files/SAP/Mobile/Bin.NET/MobileClient.exe
UFCore
    Assembly Version: 5.0.0.0
    Win32 Version: 5.11.0.40
    CodeBase: file:///C:/Program%20Files/SAP/Mobile/Bin.NET/UFCore.DLL
UFCoreExt
    Assembly Version: 5.0.0.0
    Win32 Version: 5.11.0.40
    CodeBase: file:///C:/Program%20Files/SAP/Mobile/Bin.NET/UFCoreExt.DLL
System.Windows.Forms
    Assembly Version: 1.0.5000.0
    Win32 Version: 1.1.4322.2365
    CodeBase: file:///c:/windows/assembly/gac/system.windows.forms/1.0.5000.0__b77a5c561934e089/system.windows.forms.dll
System
    Assembly Version: 1.0.5000.0
    Win32 Version: 1.1.4322.2407
    CodeBase: file:///c:/windows/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll
UFInternal
    Assembly Version: 5.0.0.0
    Win32 Version: 5.11.0.40
    CodeBase: file:///C:/Program%20Files/SAP/Mobile/Bin.NET/UFInternal.DLL
UFCommon
    Assembly Version: 5.0.0.0
    Win32 Version: 5.11.0.40
    CodeBase: file:///C:/Program%20Files/SAP/Mobile/Bin.NET/UFCommon.DLL
UFStorage
    Assembly Version: 5.0.0.0
    Win32 Version: 5.11.0.40
    CodeBase: file:///C:/Program%20Files/SAP/Mobile/Bin.NET/UFStorage.DLL
Interop.Scripting
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0
    CodeBase: file:///C:/Program%20Files/SAP/Mobile/Bin.NET/Interop.Scripting.DLL
Microsoft.VisualBasic
    Assembly Version: 7.0.5000.0
    Win32 Version: 7.10.6310.4
    CodeBase: file:///c:/windows/assembly/gac/microsoft.visualbasic/7.0.5000.0__b03f5f7f11d50a3a/microsoft.visualbasic.dll
UFControlLibrary
    Assembly Version: 5.0.0.0
    Win32 Version: 5.11.0.40
    CodeBase: file:///C:/Program%20Files/SAP/Mobile/Bin.NET/UFControlLibrary.DLL
Interop.UFGeneratorInterfaces
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0
    CodeBase: file:///C:/Program%20Files/SAP/Mobile/Bin.NET/Interop.UFGeneratorInterfaces.DLL
System.Drawing
    Assembly Version: 1.0.5000.0
    Win32 Version: 1.1.4322.2327
    CodeBase: file:///c:/windows/assembly/gac/system.drawing/1.0.5000.0__b03f5f7f11d50a3a/system.drawing.dll
MTIServices
    Assembly Version: 5.0.0.0
    Win32 Version: 5.11.0.40
    CodeBase: file:///C:/Program%20Files/SAP/Mobile/Bin.NET/MTIServices.DLL
UFDialogs
    Assembly Version: 5.0.0.0
    Win32 Version: 5.11.0.40
    CodeBase: file:///C:/Program%20Files/SAP/Mobile/Bin.NET/UFDialogs.DLL
UFIPlugins
    Assembly Version: 5.0.0.0
    Win32 Version: 5.11.0.40
    CodeBase: file:///C:/Program%20Files/SAP/Mobile/Bin.NET/UFIPlugins.DLL
System.Xml
    Assembly Version: 1.0.5000.0
    Win32 Version: 1.1.4322.2371
    CodeBase: file:///c:/windows/assembly/gac/system.xml/1.0.5000.0__b77a5c561934e089/system.xml.dll
Interop.ERRCOMPLib
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0
    CodeBase: file:///C:/Program%20Files/SAP/Mobile/Bin.NET/Interop.ERRCOMPLib.DLL
MTBLLFWInterfaces
    Assembly Version: 1.0.0.0
    Win32 Version: 5.11.0.40
    CodeBase: file:///C:/Program%20Files/SAP/Mobile/Bin.NET/MTBLLFWInterfaces.DLL
Accessibility
    Assembly Version: 1.0.5000.0
    Win32 Version: 1.1.4322.573
    CodeBase: file:///c:/windows/assembly/gac/accessibility/1.0.5000.0__b03f5f7f11d50a3a/accessibility.dll
MSY
    Assembly Version: 0.0.0.0
    Win32 Version: 0.0.0.0
    CodeBase: file:///C:/Program%20Files/SAP/Mobile/APP.Net/MSY/bin/MSY.dll
MTBLLFW
    Assembly Version: 5.0.0.0
    Win32 Version: 5.11.0.40
    CodeBase: file:///C:/Program%20Files/SAP/Mobile/Bin.NET/MTBLLFW.DLL
MTFWServices
    Assembly Version: 5.0.0.0
    Win32 Version: 5.11.0.40
    CodeBase: file:///C:/Program%20Files/SAP/Mobile/Bin.NET/MTFWServices.DLL
MTServices
    Assembly Version: 5.0.0.0
    Win32 Version: 5.11.0.40
    CodeBase: file:///C:/Program%20Files/SAP/Mobile/Bin.NET/MTServices.DLL
OnlineOffline
    Assembly Version: 1.0.2477.11060
    Win32 Version: 1.0.2477.11060
    CodeBase: file:///C:/Program%20Files/SAP/Mobile/Bin.NET/OnlineOffline.DLL
vqq-mx7r
    Assembly Version: 0.0.0.0
    Win32 Version: 1.1.4322.2407
    CodeBase: file:///c:/windows/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll
RegexAssembly40_0
    Assembly Version: 0.0.0.0
    Win32 Version: n/a
    CodeBase:
MTBLLFWMetaInternal
    Assembly Version: 5.0.0.0
    Win32 Version: 5.11.0.40
    CodeBase: file:///C:/Program%20Files/SAP/Mobile/Bin.NET/MTBLLFWMetaInternal.DLL
TLSender
    Assembly Version: 1.5.1.0
    Win32 Version: 5.11.0.40
    CodeBase: file:///C:/Program%20Files/SAP/Mobile/Bin.NET/TLSender.DLL
Interop.CRYPTINGLib
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0
    CodeBase: file:///C:/Program%20Files/SAP/Mobile/Bin.NET/Interop.CRYPTINGLib.DLL
Authentication
    Assembly Version: 5.5.0.0
    Win32 Version: 5.5.0.0
    CodeBase: file:///C:/Program%20Files/SAP/Mobile/Bin.NET/Authentication.DLL
System.Data
    Assembly Version: 1.0.5000.0
    Win32 Version: 1.1.4322.2365
    CodeBase: file:///c:/windows/assembly/gac/system.data/1.0.5000.0__b77a5c561934e089/system.data.dll
System.EnterpriseServices
    Assembly Version: 1.0.5000.0
    Win32 Version: 1.1.4322.2326
    CodeBase: file:///c:/windows/assembly/gac/system.enterpriseservices/1.0.5000.0__b03f5f7f11d50a3a/system.enterpriseservices.dll
sfabol
    Assembly Version: 0.0.0.0
    Win32 Version: 0.0.0.0
    CodeBase: file:///C:/Program%20Files/SAP/Mobile/APP.Net/MSY/bol/apps/sfabol/vba/WBIT/sfabol/bin/sfabol.dll
SSActiveTreeView.SSTree
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0
    CodeBase: file:///C:/Program%20Files/SAP/Mobile/APP.Net/MSY/Bin/SSActiveTreeView.SSTree.dll
SSActiveTreeView
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0
    CodeBase: file:///C:/Program%20Files/SAP/Mobile/APP.Net/MSY/Bin/SSActiveTreeView.DLL
AxSSActiveTreeView.AxSSTree_EventsRouter
    Assembly Version: 0.0.0.0
    Win32 Version: 0.0.0.0
    CodeBase: file:///C:/Program%20Files/SAP/Mobile/APP.Net/MSY/Bin/AxSSActiveTreeView.AxSSTree_EventsRouter.dll
Interop.UFBBInterfaces
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0
    CodeBase: file:///C:/Program%20Files/SAP/Mobile/Bin.NET/Interop.UFBBInterfaces.DLL
StdType
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.0.0
    CodeBase: file:///C:/Program%20Files/SAP/Mobile/APP.Net/MSY/Bin/StdType.DLL
Microsoft.VisualBasic.Compatibility
    Assembly Version: 7.0.5000.0
    Win32 Version: 7.10.3077
    CodeBase: file:///c:/windows/assembly/gac/microsoft.visualbasic.compatibility/7.0.5000.0__b03f5f7f11d50a3a/microsoft.visualbasic.compatibility.dll
stdole
    Assembly Version: 7.0.3300.0
    Win32 Version: 7.00.9466
    CodeBase: file:///c:/windows/assembly/gac/stdole/7.0.3300.0__b03f5f7f11d50a3a/stdole.dll
RFMobileReporting
    Assembly Version: 1.0.0.0
    Win32 Version: 5.11.0.40
    CodeBase: file:///C:/Program%20Files/SAP/Mobile/Bin.NET/RFMobileReporting.DLL
AxInterop.SAPCalendar50
    Assembly Version: 1.1.0.0
    Win32 Version: 1.1.0.0
    CodeBase: file:///C:/Program%20Files/SAP/Mobile/Bin.NET/AxInterop.SAPCalendar50.DLL
JIT Debugging **************
To enable just in time (JIT) debugging, the config file for this
application or machine (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.
For example:
<configuration>
    <system.windows.forms jitDebugging="true" />
</configuration>
When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the machine
rather than being handled by this dialog.
Its urgent, Please help me out to rectify this error.
Thanks & Regards,
Venkata Ramana

This seems like an error with standard SAP solution. I would suggest raising an OSS message and SAP should be able to help you out.
Hope this helps.
Regards,
Kaushal

Creation of System Stored Procedure in SQL Server 2012 & SQL Server 2012 R2.

Hi all,
I am stuck at a point I am looking for a system stored procedure named 'sp_dboption' in SQL Server 2012 & R2 but could not find.
Searched for it on the net and found that, this stored procedure 'sp_dboption' is now obsolete. So I tried to copy the content of 'sp_dboption' stored procedure from SQL Server 2008 R2 and create new system stored procedure with this name 'sp_dboption' in
SQL Server 2012 but was unable to create the system stored procedure.
Can you guys please tell me how to create system stored procedure in SQL Server 2012 & SQL Server 2012 R2. The reason of why I want to achieve this is because I have used 'sp_dboption' system stored procedure in my application to create a database.
As 'sp_dbotion' stored procedure is present in SQL Server 2008 R2 I am able to create the database in SQL server 2008 R2 but not in SQL server 2012.
Can you please guide me how to create system stored procedure. I am out of luck.
Please assist me, thanks & looking for help at the earliest. Hope someone will come to the fore and help me.

Hi Vishwajeet,
If you tried to create any object in the sys schema, you will get the error below.
The specified schema name "sys" either does not exist or you do not have permission to use it.
So I am afraid creating any object in sys schema is not supported by SQL Server. Here is a similar link for your reference.
How to create table in SYS schema in SQL Server?
Though sp_dboption is not in SQL Server 2012, does creating a user-defined one with the same content in 2008 make any difference in your business? You just need to specify the fully qualified name dbname.dbo.sp_dboption.
If you are still interested in creating a system sp_dboption, you can register it with the
sp_ms_marksystemobject.
See
Creating Your Own SQL Server System Stored Procedures.
Eric Zhang
TechNet Community Support

MS SQL Server system stored procedures can't be migrated into Oracle 11g

During database migration from MS SQL Server 2008 to Oracle 11g R2, if the application stored procedure invokes the MS SQL Server system stored procedures (for example: sp_getapplock, sp_releaseapplock ....), these SQL server system stored procedures can't be transferred. See following migrated Oracle application stored procedure for example:
create or replace
PROCEDURE spPwSysID_GetNextID
v_ID OUT NUMBER,
iv_SysType IN NVARCHAR2 DEFAULT NULL ,
iv_Cnt IN NUMBER DEFAULT NULL
AS
v_SysType NVARCHAR2(50) := iv_SysType;
v_Cnt NUMBER(10,0) := iv_Cnt;
v_result NUMBER(10,0);
BEGIN
--SQL Server BEGIN TRANSACTION;
utils.incrementTrancount;
v_Systype := UPPER(v_Systype) ;
IF v_Cnt < 1 THEN
v_Cnt := 1 ;
END IF;
v_result :=sp_getapplock(v_Resource => v_Systype,
v_LockMode => 'Exclusive') ;
IF v_result >= 0 THEN
BEGIN
SELECT ID
INTO v_ID
FROM PWSYSID
WHERE SysType = v_SysType;
IF SQL%ROWCOUNT = 1 THEN
UPDATE PwSysID
SET ID = ID + v_cnt
WHERE SysType = v_SysType;
ELSE
BEGIN
INSERT INTO PwSysID
( ID, SysType )
VALUES ( v_cnt + 1, v_SysType );
v_ID := 1 ;
END;
END IF;
v_result :=sp_releaseapplock(v_Resource => v_Systype) ;
END;
ELSE
BEGIN
raise_application_error( -20002, 'Lock failed to acquire to generate Cityworks Id.' );
END;
END IF;
utils.commit_transaction;
END;

During database migration from MS SQL Server 2008 to Oracle 11g R2, if the application stored procedure invokes the MS SQL Server system stored procedures (for example: sp_getapplock, sp_releaseapplock ....), these SQL server system stored procedures can't be transferred. See following migrated Oracle application stored procedure for example:
create or replace
PROCEDURE spPwSysID_GetNextID
v_ID OUT NUMBER,
iv_SysType IN NVARCHAR2 DEFAULT NULL ,
iv_Cnt IN NUMBER DEFAULT NULL
AS
v_SysType NVARCHAR2(50) := iv_SysType;
v_Cnt NUMBER(10,0) := iv_Cnt;
v_result NUMBER(10,0);
BEGIN
--SQL Server BEGIN TRANSACTION;
utils.incrementTrancount;
v_Systype := UPPER(v_Systype) ;
IF v_Cnt < 1 THEN
v_Cnt := 1 ;
END IF;
v_result :=sp_getapplock(v_Resource => v_Systype,
v_LockMode => 'Exclusive') ;
IF v_result >= 0 THEN
BEGIN
SELECT ID
INTO v_ID
FROM PWSYSID
WHERE SysType = v_SysType;
IF SQL%ROWCOUNT = 1 THEN
UPDATE PwSysID
SET ID = ID + v_cnt
WHERE SysType = v_SysType;
ELSE
BEGIN
INSERT INTO PwSysID
( ID, SysType )
VALUES ( v_cnt + 1, v_SysType );
v_ID := 1 ;
END;
END IF;
v_result :=sp_releaseapplock(v_Resource => v_Systype) ;
END;
ELSE
BEGIN
raise_application_error( -20002, 'Lock failed to acquire to generate Cityworks Id.' );
END;
END IF;
utils.commit_transaction;
END;

APP-PAY-06153 SYSTEM ERROR:Procedure at step 1

Hi All,
I select Inventory ,Vision Operations(USA) responsibility---------->Setup----->Oraganisations----->organisations
when i selected that getting the below error.
APP-PAY-06153 System Error:Procedure INIT_FORMS STEP 1
cause: The Procedure INIT_FORMS created an error at STEP 1
ACTION: contact your system administrator quoting the procedure INIT_FORMS and step 1.
any suggesions on this.
Regards,
Nag.

931161 wrote:
I having the same issue in CA Super HRMS Manager Responsibility>Enter and Maintain Form when I have tried to open giving me this error.Do I need to set up under this responsibility ?
profile options HR:Security Profile:What value to select?
and HR:Business Group :What value to select?
HR:User Type ...What value to select?It depends on your setup.
http://www.oracle.com/pls/ebs121/ranked?word=HR:Business+Group&partno=e13477
http://www.oracle.com/pls/ebs121/ranked?word=HR:Business+Group&partno=e13471
Thanks,
Hussein

APP-PAY-06153: System Error : Procedure pay_us_emp_dt_tax_rules.insert_fed

Dear Friends,
I'm finding the below mentioned error while I'm attaching the salary basis & saving the same,
APP-PAY-06153: System Error : Procedure pay_us_emp_dt_tax_rules.insert_fed_tax_row - ORA-20001: &1 element does not exist or has not linked to pay at step 4.
Can any1 pls guide me to ahy facing the above error?
Guru K

Guru2Win wrote:
Dear Friends,
I'm finding the below mentioned error while I'm attaching the salary basis & saving the same,
APP-PAY-06153: System Error : Procedure pay_us_emp_dt_tax_rules.insert_fed_tax_row - ORA-20001: &1 element does not exist or has not linked to pay at step 4.
Can any1 pls guide me to ahy facing the above error?
Guru KPlease see if these docs help.
Error Saving A Salary Basis - pay_us_emp_dt_tax_rules.Insert_fed_tax_row [ID 302878.1]
DATA: HR_ENTRY.GET_ELIGIBILITY_PERIOD HAS CREATED AN ERROR AT STEP 4 [ID 967419.1]
There is No List of Values (LOV) for the SUI State on the Federal Tax Record [ID 1508293.1]
Thanks,
Hussein

Replicating System Stored Procedures in MSA Setup

I started replicating system stored procedures in my MSA environment due to the fact that commands such as sp_rename was not making it to my MSA server. This caused some issues downstream resulting in the DSI goign down and having to manually apply these statements on the target server.
My question is, are there any cons/drawback to enabling such option
In reading the manual one of the requirements was that
Make sure that both the primary and replicate data servers are the same version of Adaptive Server.
I am Replication from Sybase Cluster Edition 15.7 SP131 to Sybase SMP 15.7 SP131. So far I have not encountered any issues but I don't like surprises.
Other requirements are met
When replicating DDL – the primary and replicate databases must have the same login names and passwords; the DSI uses the original server login name and password to log in to the replicate database.
For me the logins are identical on both servers so this is not an issue
To replicate DDL and system procedures:
Mark the primary database using sp_reptostandby.
Set the RepAgent parameter send warm standby xacts to true—even if there is no standby database
I also have a warm standby setup and I am using the logical connection as the primary dataserver so these conditions are also met
Thanks

I started replicating system stored procedures in my MSA environment due to the fact that commands such as sp_rename was not making it to my MSA server. This caused some issues downstream resulting in the DSI goign down and having to manually apply these statements on the target server.
My question is, are there any cons/drawback to enabling such option
In reading the manual one of the requirements was that
Make sure that both the primary and replicate data servers are the same version of Adaptive Server.
I am Replication from Sybase Cluster Edition 15.7 SP131 to Sybase SMP 15.7 SP131. So far I have not encountered any issues but I don't like surprises.
Other requirements are met
When replicating DDL – the primary and replicate databases must have the same login names and passwords; the DSI uses the original server login name and password to log in to the replicate database.
For me the logins are identical on both servers so this is not an issue
To replicate DDL and system procedures:
Mark the primary database using sp_reptostandby.
Set the RepAgent parameter send warm standby xacts to true—even if there is no standby database
I also have a warm standby setup and I am using the logical connection as the primary dataserver so these conditions are also met
Thanks

APP-PAY-06153: System Error : Procedure pay_us_emp_dt_tax_rules.insert_fed_tax_row - ORA-20001: &1 element does not exist or has not linked to pay at step 4

Hi Experts,
I'm finding the below mentioned error while I'm saving assignment with Salary Basis, Location and Payroll.
APP-PAY-06153: System Error : Procedure pay_us_emp_dt_tax_rules.insert_fed_tax_row - ORA-20001: &1 element does not exist or has not linked to pay at step 4.
Please note that I am able to save the record if I do not any one of Salary Basis, Location. Payroll. It is basically happening on creating default tax.
Can anyone pleas let me know if you have facing the above error and resolved?
Guru

Hi Guru,
Did you check -
Error Saving A Salary Basis - pay_us_emp_dt_tax_rules.Insert_fed_tax_row (Doc ID 302878.1)
Cheers,
Vignesh

Programmed system maintenance

I read that OSX has pre-programmed system maintenance and there is discussion on whether the computer should be turned off at night.
Is there someplace I can check or reset my system maintenance?

To check when your Periodic Maintenance Scripts, which I hope is what you want to know, open Terminal and type this exactly:
ls -al /var/log/*.out
Press Return
and you should see three lines of info, one for each script: Daily, Weekly & Monthly. The date and time they were last run is in each line.
To manually run the scripts open Terminal and type:
sudo periodic daily weekly monthly
Press return. You will be prompted for your Admin password and you need to type this into Terminal. Be warned, it might take a long time to run the scripts.
For more info checkthe most excellent:
The X Lab
Hope this helps
MacBook Pro 15" Mac OS X (10.4.9) 1.83 GHz Intel Core Duo

System refresh procedure!!!

Can anyone of you please help me in understanding the system refresh procedure??What it is used for and how does it help an organisation!!!

Read
http://help.sap.com/saphelp_nw70/helpdata/EN/a2/2f0c173a5e43d19585724239ff4de7/frameset.htm
Markus

System Maintenance Procedures

Similar Messages

Maybe you are looking for