<![CDATA[Saudico]]> <![CDATA[Command for Changing password In Oracle.]]> Command for changing password

conn sys as sysdba

password:

alter user fbdata identified by fbdata;

]]> <![CDATA[Error encountered loading library:GailWrapper.dll]]> SYMPTOMS
Below Error comes up once logging on to MC -> Processing Purchase Orders via email- any B2B action

Error encountered loading library:GailWrapper.dll




CAUSE
C++ redistributable Package has not been installed properly, or .Net 3.5 is not enabled.


SOLUTION
If below error referring to the GailWrapper.dll does appear than reinstall the Microsoft Visual C++ Redistributable Package (x86) . The exe file (vcredlist_x86.exe) can be found in any installed Mataerials Control Client directory. Simply double click on the exe for installation. Please reboot the PC after the install completed.

Verify that .Net 3.5 is enabled ( Control Table ->Program Features -> Turn Windows features on or off


Regards
]]> <![CDATA[Error When Exporting Invoices to Back Office]]> In MC, we get an Error message when we try to export the invoices to BO after changing to VAT 15%.


You need to do as below to resolve this matter.

You need to change the VAT15% back to VAT5% to book the invoices to the back office. Once you had done the booking, you can go back to VAT15%.

This error is coming due to the receiving is in VAT5% and now the attach rates to the supplier are VAT15%.


Regards

]]> <![CDATA[Error: Exception has been thrown by the target of an invocation.]]> Error: Exception has been thrown by the target of an invocation.

           Inner Exception: 

           Padding is invalid and cannot be removed.



Reason : During the Installation of Multiple MC Clients different Security Containers have been used. i.E.: A machine had CAPS-LOCK in place , on the next machine the password will be rejected, so the               user sets up a new security password, the one that had been used with the first installations of which he thinks that this is the correct one (but actually it is different due to CAPS-LOCK).

             So now when accessing MC and opening Modules on the first machine (with the other Security Container) the error will be triggered. While on other PC's where the client has been installed MC                works properly.


Solution:

You must obtain several files from a PC where Materials Control is working properly.

Using the Secure Config Tool access the third tab : Key Containers Management. Select the Materials Control Key and right click. Choose the option : Export Key Container.
The MaterialsControl.xmlfile will be exported.

Take the following files from the PC with the working Materials Control Client : fmlogin.ini, MC.config,Setup.mcd and the RSA Key that had been exported prior via the Secure Config.exe (MaterialsControl.xml).

Now on the PC where the MC Client triggers the errors, Import the Key Container wit the secure Config tool  : Proceed to the third Tab Key Containers Management and select the option : Import Key Container, using the MaterialsControl.xml that was exported prior from the other (working) machine.

All other files , the fmlogin.ini,MC.Config,Setup.mcd must be copied in the Materials Control folder directly in the root directory of the Materials Control client. All will be working properly after.

 

]]> <![CDATA[Export to excel In MC]]>  

Export to excel not working.

 

Need to copy this line to the sql.ini.

[odbcrtr]

remotedbname=FMEXCEL,DRIVER={Microsoft Excel Driver (*.xls)};DBQ=fm_excel.xls;DefaultDir=C:\Program Files\Materials Control\LOG;ReadOnly=;

or 

 

Please Open Configuration (System>>Configuration) 

SET FBV8.ini >> Path >> XLSTEMPLATE = templates\default_tmpl.xls

Save it and logout and login again.

 

]]> <![CDATA[MC - Report Builder 6.x]]>
https://www.dropbox.com/s/lvvizdgyqcczhb4/rb6.zip?dl=0

https://drive.google.com/open?id=1ZsH09bFYZTFa4hZ3mf8dGK_BzbcVpAln

]]> <![CDATA[RMBackup : The DB does not start after the RMAN backup not worki...]]>
The DB does not start after the RMAN backup not working and the allocated space is used.


Archive Parameter / RMBACKUP / BACKUP / MC / ORACLE /


Solution I:

Enter user-name: / as sysdba

SQL> startup mount

SQL> alter system set db_recovery_file_dest_size=8G scope=both;

SQL> shutdown immediate;

SQL> startup


*******************************
Solution II:

SQL>STARTUP MOUNT

SQL> Show parameter DB_RECOVERY_FILE_DEST_SIZE;

SQL> ALTER SYSTEM SET DB_RECOVERY_FILE_DEST_SIZE = 80G SCOPE=BOTH ;

SQL>ALTER DATABASE OPEN;


D:\OracleApp\flash_recovery_area\fmcagt\ARCHIVELOG

Delete the old log file to create space.

*************************************

to set the path to oracle home db ...

SQL> Show parameter DB_RECOVERY_FILE_DEST_SIZE;

SQL> ALTER SYSTEM SET DB_RECOVERY_FILE_DEST_SIZE = 60G SCOPE=BOTH ;

***************************************************
Solution III:

Steps to activate the archive log

To bring the database in archive mode in opera / or any other databases follow these steps.

Login into sqlplus

Start->Run->SqlPlus

Enter user-name : sys@opera as sysdba (@opera can be vary as per the alias name of the database)
password : opera10g (This is the default password of opera database this can be vary for some other products databases)


SQl> Shut immediate;
After the database was successfully shut down.
Change the initialization parameter file and unmarked the Archive path and format lines.
SQL>startup mount;
SQL>alter database archivelog;
SQL>alter database open;


If you want to see where the archives are getting generated hit the below command.

SQL > Archive log list;

Here you will find the path where the archives are getting generated.

Regards,
Mohammad Abdul Khader..]]> <![CDATA[SR 314088925621 : Simphony (Hosted)MC interface ,Revenue not impo...]]> <![CDATA[Unable to check user Out of office]]>

Solution:

The issue is , If a user ‘A’ is already assigned as Stand by with other user ‘B’ , then other users can’t be a stand by of user ‘A’ ,the stand by option will disabled in user ‘A’ configuration.

First we have to remove the user ‘A’ from the stand by option of user ‘B’ , then the stand by option will enabled for user ‘A’.

In the case of big properties , it will be difficult find the user ‘B’ and some time it will be deactivated user.
So you can use following sql query to find the user and stand by user.

1.select bst_id ,bst_name form besteller where bst_name like ‘A%’;
2.select bst_id,bst_name from besteller where bst_standin=(bst_id of user A);
3. update besteller set BST_OUTOFOFFICE=0 ,BST_STANDIN=null where bst_id = (bst_id of user B);

Solution Provided by Mr. Mohammed Haris

.]]> <![CDATA[Unlocking the user in Oracle.]]> command for unlocking account in oracle

conn sys as sysdba

password : system or oracle

alter user system account unlock;

 

***********************

Command for changing password

conn sys as sysdba

password:

alter user fbdata identified by fbdata;

]]> <![CDATA[VAT Implementation Doc]]> SES VAT Implementation Guide lines for all the modules.]]>