1. If the hotel or the Ministry changes the API credentials (Hotel ID, User Name, Password or API Key) of the NTMP platform (Fig.2)
2. If the hotel changes the Windows username or their password which is set to run the task scheduler
3. If the hotel add or edit firewall rules that would block the uploading of data to the NTMP platform
4. If the hotel wants to add, edit or change any of the following configurations in the PMS systems
   
   1. Room Types
   2. Nationality Codes
   3. Payment Types
   4. Cancellation Reasons
5. If the hotel finds out any abnormal logs generated in the PMS Interface PC where the NTMP is configured
6. If the NTMP portal’s “View Integration Data” section is not showing an updated record of the recent activity (date/time)

Please feel free to contact us, if you need any clarifications or explanations on this subject. Please be aware that Saudico Electronic Systems will not take any responsibilities and/or liabilities in the issues that are caused beyond its control. Every hotel is expected to closely monitor the integration on a daily basis and keep us informed about any abnormality, to avoid any actions by the ministry.


Fig.1 / Fig.2

 Kindly take a note for above Article Title Forecast Processor and Shared Pay Master.

Kindly be requested to release / check out all the Pay Masters (PM) rooms from the Opera PMS system which has shares inside.

It is slowing down the work as well as creating thousands of forecast events and remaining the real time job to be executed in pending and not updating so many jobs.

 
We hope this message will be taken on a very high priority to have always a smooth work in Opera PMS.

Regards,
Duste Mojibullah Omar

Client Relation & Support Manager

Here is a little trick to make OPERA noticeable quicker on remote connections (especially RDP):

When connected to the remote server or workstation where you want to open OPERA, prior to logging into OPERA, click on START -> Settings -> Control Panel

Find the “JInitiator” icon

You will see a white box on the first tab (“Basic”) called “Java Runtime Parameters”

Enter the following line in there:
-Dsun.java2d.noddraw=true

This will force Java to only refresh the piece of OPERA screen, which actually has changed and not the entire screen.

As per Opera development team, this change is harmless and will have no negative impact on the Operation of OPERA.

This is also one of the solution for some refresh issue, not only for remote desktop connection, but also for some client/workstation connection.

Problem :

Opera SMT backup failed with ORA-01555: snapshot too old: rollback segment number 19 with name "_SYSSMU19_255734752$" too small. 

We faced the similar issue earlier but after running the export through data pump issue got resolved. Export completed successful in a very short time. 

But in this property we are facing altogether different issues while running backup with the data pump. 

Kindly please have a look on urgent basis.


Reply :

Reviewed the notes and the current situation is that the Export trough the SMT tool is not producing Ora-1555 anymore but not Compressing the files. If started manually all works fine. 

If not already mentioned here: Please note that the (S)hema(M)anagement(T)ool is not a backup solution. It is used for schema maintenance and provides a backup solution. To have a proper backup you should ensure that the processors are stopped during the export. 

Our suggested Backup solution is RMAN. Of course you can schedule the SMT export using the task scheduler. But as each installation is different we can only support the manual export. 
You as an Oracle Partner should be able to setup a RMAN backup and troubleshoot the Windows Taskmanager. In most cases it is the "RUN with highest privileges" checkbox or a unknown path for the ZIP/7ZIP exe when started with a different user in Task scheduler