Title: Hiring an new DBA, interview tips
sraffey - January 15, 2006 11:54 PM (GMT)
Hi guys,
I don't know if this is the best place to be posting this. Bu we're hiring a new DBA and have three people coming in for interviews next week. (Our DBA won the lotto if you can believe that, a good portion of it anyway). :blink:
Anyway. So I was hoping someone could give us some tips on what to ask during the interview to make sure we have a good candidate for a Lawson DB2 DBA. No one here really knows DBA type lingo other than our sys-admin, and he's not going to have enough time to sit in too many interviews. Oh and I'm probably going to need the answers too :D
If this is not the best place to post this please move my post or let me know where I should re-post it. I just have to hope that my candidates won't see this post :rofl:
Thanks
Sam
Phil Feller - January 16, 2006 06:16 AM (GMT)
I'd worry mostly about finding a solid DB2 DBA, and not concentrate too much on the Lawson-specific aspects of the job. A book such as "Ace the Technical Interview" would give you a good selection of questions (and answers) to help you determine the candidate's level of ability.
If someone claims Lawson DB2 experience, ask them what file holds the configuration information needed to connect a data area to the DB2 database ($LAWDIR/dataarea/IBM). Then ask them what they need to put into that file in order to collect database timed statistics (TIMESTATS=TRUE; they get extra credit if they know about USER_FILTER and PROGRAM_FILTER). Finally, ask them how to create a view in dbdef.
jkerry - March 16, 2006 07:14 PM (GMT)
Hmm, Phil, How DO you create a view in dbdef?
cjmart - March 16, 2006 08:04 PM (GMT)
Article ID: 85704
How do I make a new Oracle database view accessible via Lawson 4GL applications and Enterprise Reporting?
Description:
I have created a view in my Oracle database. How do I make this view accessible via Lawson 4GL applications and Enterprise Reporting?
Resolution:
Create a table in dbdef with the same structure as your new Oracle database view.
At a Lawson INSIGHT (LID) prompt, type dbdef productline and press Enter.
Press F6 (Define) and choose option A (Files).
Type a name for your file in the File Name field. (Give the file name the same name as your database view. In addition, give the file a system code, a prefix, and fields that are the same name, size, and type as the fields in the view.)
Create one index for this table, making this new index your primary index.
Press the Enter key a few times to return to the main dbdef screen.
Create a ‘view’ database space.
Press F6 (Define) and choose option E (Database Space).
Create a database space. Specify a Type of "Oracle". Define any values you want in the Table Space and Index Table Space fields. Set the Is View field to Yes.
Press the Enter key a few times to return to the main dbdef screen.
Assign your new database space to your new table.
Press F6 (Define) and choose option C (Data Areas/Data IDs).
Press F6 (Define) again. Choose option B (File Sizes and Database Space).
Scroll down to your new table. Tab over to the Database Space column and press F4 (Select).
Select the database space you just created.
Press the Enter key a few times to return to the main dbdef screen.
Exit dbdef.
Apply your changes to the current productline dictionary.
Type blddbdict productline and press Enter.
Type dbreorg productline and press Enter.
Your new Oracle database view is now accessible via Crystal Reports, the Lawson OLE DB Query Builder, and any Lawson 4GL programs that you may create.
Additional Information:
Lawson's Global Support Center (GSC) provides this document to use at your own risk. The GSC does not support this procedure, and does not support custom views.
lawson - March 16, 2006 08:28 PM (GMT)
Just a suggestion: This would make a great article in the Members Articles section if you want to post it there cjmart.
schroncd - March 16, 2006 10:49 PM (GMT)
Word of caution.. You don't want to become a separate repository of GSC articles. Lawson doesn't mind you referenceing article numbers and making quotes from them, but I'd be leery of posting entire articles. Another site which all we oldtimers know and loved had some difficulties along those lines.
lawson - March 16, 2006 11:06 PM (GMT)
Good point, maybe rewrite that one.