Lessons Learned - Restoring from time machine and filevault

A very hard lesson I learned over the weekend: time machine will not back up any files configured with Filevault. My personal files, videos and pictures ALL KA-POOF because the user data was not backed up.

After restore I get a message saying I cannot login to file vault using 'mina' at this time. I went thru phases or anger, frustration, denial and finally acceptance that I can no longer restore all files along with my memories. They are forever LOST somewhere on my imac drive as little fragment that can never be joined or restored. Fudge!!!!! 

Merry Christmas!

/ LB: Unexpected error in LG Layer

This error stuck in SM58 related to workflow processing. Clicking F6 (Execute LUW) processes but the issue is why it's getting stuck.

Analyze the stuck RFC and look at and/or check the RFC destination with Trace. Check RFC trace logs to see any error. For this case, trace showed error in R3name, pointing to the wrong SID. So, fixed the RFC, changed the logon properties and there's no more RFC stuck in tRFC.

MAXDB Install

Something interesting... I installed this database in my Vista workstation. This is not part of my work but it's nice that I can install this database in my workstation so easily. So, I'll be doing a lot of updating on this from now on.

Installation

As usual, SAP documents can be very confusing (at least for me). I had to dig into the install docs to find out what I need to do, reinstall at least twice just to get things right to follow the tutorial.

So, here it is, totally learned something about this database from an install perspective.

1. Download the free install in SAP website. I would start with the home db of MAXDB, which is MaxDB and SAP liveCache. On the right, click on the link below Download which would take you MaxDB Downloads.

My operating system is Vista (32-bit), so I chose SAP MaxDB 7.6 for Windows (x86, 32-bit. Note that the links may vary in time and it will need a login for it to continue.

While downloading, go to the complete MAXDB Documentation page to read more information.

2. When download completes, execute the downloaded file and go thru the instructions provided here.

3. After setup is finished, download and install DB Manager and SQL Studio.

4. Reboot (as required by install).

5. Run Database Manager (as Admin) and add database instance DEMODB.

6. Connect to DEMODB. The error (below) would occur due to some incompatibility issues with Vista but as soon as you press OK, the status of the database is ONLINE (and colored green).

7. Create additional database users. Follow instructions from this link.
8. Loading Tutorial and Demo Data. From the Database Manager, click on Configuration and click Load Tutorial (more info here.

Check if it's loaded by viewing the table in SQL Studio. From the Database Manager, click menu Tools -> SQL Studio. Connect to the database by clicking the Key icon, supply the necessary login information needed to connect. Click on Indexes, it should have the HOTEL schema.

Ok, gotta go. Til next time.

RHPROFL0

Short text

Generate User Authorizations

Description

Functions of Report RHPROFL0

Report RHPROFL0 creates authorization profile assignments for users in an organizational structure. A distinction is made between standard authorization profiles and authorization profiles for structural PD authorizations. In addition, user roles and their profiles are assigned.

Using the start evaluation path PROFL0 , the system finds and temporarily saves all users in the structure. Starting from these users, on a key date, the system reads all valid related objects for which infotype 0106 (standard authorization profile) and / or 1017 (authorization profile for structural PD authorizations) is maintained, up to the next highest organizational unit. This means that the superior organizational units are not taken into account.

The relevant object types are job (C), position (S), organizational unit (O), task (T), task group (TG), workflow template (WS), workflow task (WF), standard task (TS), work center (A), and responsibilities (RY). In addition, all user roles (AG) and their standard authorization profiles are included.

The system then checks whether the users found are already created in the system. This is necessary because in infotype 105 (subtype 0001) of a person, users can be entered that are not created in the system.

If a user is not yet in the system, it is automatically created. Then the system enters authorization profiles for all users found in the organizational plan.

You can check the results for the standard authorization profiles and user roles using transaction SU01 . The structural PD authorizations can be displayed using transaction OOSB .

Report Parameters

1. Start object

Starting from a Start object , the Evaluation path searches for all assigned users in the organizational plan. If you enter a user as start object, the system selects only that one user. The Key date is the date on which the relationships are evaluated. If the Testrun parameter is set, the system only finds and evaluates the authorization profiles, without assigning them to the corresponding users.

2. Generate authorization profiles

If the Generate standard authorizations parameter is set, the corresponding standard authorization profiles are changed. Likewise for the Generate PD authorization profiles parameter and the structural PD authorization profiles. If the respective parameter is not set, the authorization profiles assigned to the users remain unchanged.

3. Delete manually maintained authorization profiles

• Standard authorizations
  
  Caution: if the Delete standard authorizations parameter is set, all user profiles that were manually maintained via transaction SU01 are deleted and only the new authorizations that were derived from the organizational plan are reassigned. An exception is the SAP_ALL profile. If you want to delete this profile too, the Delete profile SAP_ALL must also be set.
  
  If this parameter is not set (default setting), the system deletes only those authorization profiles originating from a user role that is no longer assigned to the user, according to the current organizational plan. These authorization profiles are also marked as generated profiles in transaction SU01 . All other manually maintained authorization profiles (infotype 1016) remain in existence.
  

• Structural PD authorizations
  
  Caution: if the Delete PD authorizations parameter is set, the system deletes all the structural PD authorization profiles that were manually maintained in table T77UA . This includes the delimited profiles. Note that a user that has no structural authorization profiles automatically gets the authorization profile SAP* (in other words authorization for all organizational objects). This profile, however, is not entered in table T77UA .
  
  If the parameter is not set (default setting), the system deletes only those authorization profiles that were assigned via report RHPROFL0 , as these were marked by the new program.
  

4. Invalid users

If the Include invalid users parameter is set, the system also selects those users that are no longer valid on the key date, but that still exist in the system.

5. New users

If the Generate new users parameter is set, users are generated that were assigned to a person in infotype 105 (subtype 0001) but not yet created in the system. If the Transfer relationship period between person and user is also set, the new users are created with the same validity period that is maintained in infotype 105 (subtype 0001) for the person. If the parameter is not set, the new users are created from the key date to the latest possible date (31.12.9999). Over the User data parameter, the system assigns the Initial password and the User group .

Application Log

All messages that are generated during the profile comparison are saved in the application log. The application log is newly generated each time the report RHPROFL0 is run. You can display it by choosing theDisplay log(s) pushbutton, which is at the top of the output list.

If the report is planned in a batch job and automatically executed, the output list is printed out. In that case, you can see the application log by choosing transaction SLG1 . On the selection screen, enter 'RHPROFL0' as the Object . The Subobject and Ext. number fields remain empty.

- SAP Help -

SCOT Wait times

Just learned a trick today. User was wondering why her e-mail took long to be sent when executing a custom program and sending e-mails thru her distribution list.

As she sent one request while we're chatting, request has a wait time of about an hour before it can be sent. RSCONN01 program runs every 10 minutes but SCOT for some reason scheduled an hour in the queue for this request to be sent.

Turns out that the user's time zone (in CET) is not similar to system time so system time (UTC), so she changed her time zone to UTC and sent out another e-mail and was immediately sent.

SFTP error

Problem error:
Trying to use sftp to remote host with port 115 open for secure FTP...

ppan08:xxxusr 1> sftp xxxftp@x.xx.xxx.xxx
Connecting to x.xx.xxx.xxx...
PRNG is not seeded
Connection closed

Solution:

1. Executed via root id and it was successful.
sftp xxxftp@x.xx.xxx.xxx
Connecting to x.xx.xxx.xxx...
The authenticity of host 'x.xx.xxx.xxx (x.xx.xxx.xxx)' can't be established.
RSA key fingerprint is 93:96:47:a0:92:dd:db:e7:3c:64:b1:49:44:53:a5:32.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added 'x.xx.xxx.xxx' (RSA) to the list of known hosts.
xxxftp@x.xx.xxx.xxx's password:
sftp> put /tmp/test.txt
Uploading /tmp/test.txt to /FTPDIR/test.txt
/tmp/test.txt 100% 5 0.0KB/s

2. Looking further into previous error encountered: "PRNG is not seeded"

/dev files (random and urandom) permission changed to r for the "seeding" to be executed. It was detected that files only have crw access for the file owner and no permission to anyone else (crw------- ). Hence, this is the reason why it worked with root id.

Upon changes to the permission of the files (crw-r--r--), sftp worked with any id with the same results above.